public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "avi at checkpoint dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/10510] Use of follow-fork-mode child causes GDB to crash
Date: Tue, 01 Sep 2009 10:00:00 -0000	[thread overview]
Message-ID: <20090901100012.15324.qmail@sourceware.org> (raw)
In-Reply-To: <20090811121103.10510.avi@checkpoint.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.


  parent reply	other threads:[~2009-09-01 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 12:11 [Bug gdb/10510] New: " avi at checkpoint dot com
2009-08-16 14:05 ` [Bug gdb/10510] " pedro at codesourcery dot com
2009-09-01 10:00 ` avi at checkpoint dot com [this message]
     [not found] <bug-10510-4717@http.sourceware.org/bugzilla/>
2012-10-24 15:42 ` palves at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090901100012.15324.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).