Re: kern/54268: (old) gdb has issues after recent ptrace changes

[Kamil Rytarowski <n54%gmx.com@localhost>]

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

From: Kamil Rytarowski <n54%gmx.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/54268: (old) gdb has issues after recent ptrace changes
Date: Tue, 4 Jun 2019 15:59:41 +0200

 On 03.06.2019 17:45, Martin Husemann wrote:
 > The following reply was made to PR kern/54268; it has been noted by GNAT=
 S.
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: kern/54268: (old) gdb has issues after recent ptrace change=
 s
 > Date: Mon, 3 Jun 2019 17:41:26 +0200
 >
 >  When telling gdb to create a core in this state, the core is unusable:
 >
 >  [New process 1]
 >  Core was generated by `gdb'.
 >  Program terminated with signal SIGABRT, Aborted.
 >  #0  0x00000000422ff264 in ?? ()
 >  .gdbinit:189: Error in sourced command file:
 >  gdbpp:5: Error in sourced command file:
 >  Scripting in the "Python" language is not supported in this copy of GDB=
 .
 >  (gdb) bt
 >  #0  0x00000000422ff264 in ?? ()
 >  Backtrace stopped: previous frame identical to this frame (corrupt stac=
 k?)
 >
 >  Martin
 >
 >
 
 Is this old GDB the one just before 8.3 upgrade and with my changes
 included? If not and this is a older version of GDB without my patches
 included (committed on May 3rd), then I would recommend closing it.
 
 There are still races in the kernel and firefox is one of my test
 targets for multiprocess and multithreaded applications.
 
 There are few problems identified (at least 3) that still make LWPs
 racy, but it should work better than ever for non-complex applications.
 
 Once I will sort out them (with an intermediate work on vfork(2)), I
 will be back to this thread.