public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/13700] should allow CLI to switch thread on event Date: Thu, 16 Feb 2012 18:09:00 -0000 [thread overview] Message-ID: <bug-13700-4717-VMmPsJUAgQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13700-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13700 --- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-02-16 18:08:16 UTC --- My scenario was something like: debug 'make' in multi-inferior mode, run it in the foreground, lots of new inferiors are created and destroyed, then one of them crashes. Then I got output like this: [New process 2800] process 2800 is executing new program: /home/tromey/gnu/archer/Multi/crasher Program received signal SIGSEGV, Segmentation fault. 0x000000000040047f in main () at crasher.c:5 5 *x = 52; ... but I was actually debugging the original inferior, which is still running: (gdb) info inferior Num Description Executable 7 process 2800 /home/tromey/gnu/archer/Multi/crasher * 1 process 2792 /usr/bin/make I just found this very surprising. In fact the first time I didn't realize what had happened and I assumed there was a gdb bug, because I saw a crash (which visually is indistinguishable from the familiar single-inferior single-thread case) and tried to bt: (gdb) bt Target is executing. -- 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.
next prev parent reply other threads:[~2012-02-16 18:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-16 14:51 [Bug cli/13700] New: " tromey at redhat dot com 2012-02-16 15:15 ` [Bug cli/13700] " palves at redhat dot com 2012-02-16 18:09 ` tromey at redhat dot com [this message] 2012-02-16 18:30 ` palves at redhat dot com 2012-02-20 19:11 ` palves at redhat dot com 2014-11-04 15:02 ` tromey at sourceware dot org
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=bug-13700-4717-VMmPsJUAgQ@http.sourceware.org/bugzilla/ \ --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: linkBe 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).