[Bug gdb/10510] Use of follow-fork-mode child causes GDB to crash

[Bug gdb/10510] Use of follow-fork-mode child causes GDB to crash

[palves at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=10510

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |palves at redhat dot com
         Resolution|                            |FIXED

--- Comment #3 from Pedro Alves <palves at redhat dot com> 2012-10-24 15:42:02 UTC ---
Yet many more fixes in the fork support have gone in since that snapshot.
Our fork tests in the testsuite pass, so I'm closing this.  If this is still a
problem with current GDB, please reopen.

Thanks.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug gdb/10510] Use of follow-fork-mode child causes GDB to crash

[avi at checkpoint dot com]

------- Additional Comments From avi at checkpoint dot com  2009-09-01 10:00 -------
I tried using a snapshot from August the 18th (version 6.8.50.20090817-cvs). 
Machine configuration and program compilation is as before.

Using this snapshot, GDB does not crash, yet it fails to debug the child. 
Following is GDB output:

  (gdb) set follow-fork-mode child
  (gdb) c
  Continuing.
  [New process 3538]
  [Thread debugging using libthread_db enabled]
  Executing new program: <our child program>
  Error in re-setting breakpoint 1: Can't find member of namespace, class, 
struct, or union named <function with break>
  Hint: try '<function with break><TAB> or '<function with break><ESC-?>
  (Note leading single quote.)
  [Thread debugging using libthread_db enabled]
  [New Thread 0x6cbb2bb0 (LWP 3542)]
  infrun.c:2398: internal-error: handle_inferior_event: Assertion `inf' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n
  infrun.c:2398: internal-error: handle_inferior_event: Assertion `inf' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) y
  (gdb) bt 
  Target is executing.
  (gdb) quit
  A debugging session is active.
   
          Inferior 2 [process 3538] will be detached.
   
  Quit anyway? (y or n) y
  Detaching from program: <our child program>, process 3538

[Please note that the child program crashed following the detach (this crash 
does not happen when not debugged).]

Following is the backtrace of GDB, extracted from the GDB core file:

  (gdb) bt
  #0  0x77d7bd4f in sigpending () from /lib/tls/libc.so.6
  #1  0x77d7d555 in _quicksort () from /lib/tls/libc.so.6
  #2  0x0808a4ac in ?? ()
  #3  0x77e89ce4 in tmpbuf.0 () from /lib/tls/libc.so.6
  #4  0x00000000 in ?? ()


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1


http://sourceware.org/bugzilla/show_bug.cgi?id=10510

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug gdb/10510] Use of follow-fork-mode child causes GDB to crash

[pedro at codesourcery dot com]

------- Additional Comments From pedro at codesourcery dot com  2009-08-16 14:05 -------
Many bugs were fixed in the follow-fork-mode support since 6.8 was
released, over a year ago.  In addition, the clear_lwpid_callback function
was deleted from CVS on 2008/03.  Please try a recent snapshot or CVS HEAD,
and let us know how it goes.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=10510

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.