Re: kern/53120 (gdb issues with threaded programs)

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR kern/53120; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: gnats-bugs%NetBSD.org@localhost, martin%NetBSD.org@localhost, christos%NetBSD.org@localhost, kamil%NetBSD.org@localhost
Cc: 
Subject: Re: kern/53120 (gdb issues with threaded programs)
Date: Thu, 21 Jun 2018 16:18:37 +0300

 I'm also having gdb issues with threaded programs in -current, similar
 to those Martin reported in March, and they are impeding my attempts
 to track down other bugs.
 
 Here is a shell script I'm currently using to test for the problem:
 
 sysctl -w security.pax.mprotect.enabled=0 || true
 sysctl -w security.pax.mprotect.ptrace=0 || true
 cat <<EOF >test.gdb
 b main
 run +time=1 +tries=1 @127.0.0.177
 b write
 cont
 cont
 cont
 cont
 cont
 EOF
 gdb --batch -x test.gdb dig >gdb.out
 cat gdb.out
 ! grep SIGSEGV gdb.out
 
 This will exit with a nonzero status if gdb is triggering spurious
 SIGSEGVs, as it does in -current.
 
 I believe the problem was introduced by Christos' import of gdb 8.0.1
 in November 2017.  I have not run a full bisection, but I manually ran
 the above test against some source dates around that time, and they show
 the test passing before the import and failing after it:
 
 2017.05.01.12.29.40   pass
 2017.11.28.15.31.33   pass
 2017.11.30.14.51.01   fail
 2017.11.30.15.26.57   fail
 2017.12.02.22.51.22   fail
 2018.06.19.09.25.13   fail
 
 Would anyone object to reassigning this PR from Kamil to Christos?
 -- 
 Andreas Gustafsson, gson%gson.org@localhost