public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tamas at eisenberger dot hu" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/13653] ~"inferior.c:61: internal-error: set_current_inferior: Assertion `inf != NULL' failed. Date: Thu, 02 Feb 2012 16:29:00 -0000 [thread overview] Message-ID: <bug-13653-4717-pH5GqAS56V@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13653-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13653 --- Comment #2 from Eisenberger Tamás <tamas at eisenberger dot hu> 2012-02-02 16:28:54 UTC --- Well, I can't reproduce this without eclipse, so I'll have to attach to the gdb process eclipse starts.. I'll try to do that, but a good example of doing such would be helpful. Should I use the same (currently HEAD compiled with -g -O0) gdb to debug, and be debugged? P.S.: Thanks for the fast reply! -- 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-02 16:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-02 14:33 [Bug c++/13653] New: " tamas at eisenberger dot hu 2012-02-02 14:34 ` [Bug c++/13653] " tamas at eisenberger dot hu 2012-02-02 15:19 ` tromey at redhat dot com 2012-02-02 16:29 ` tamas at eisenberger dot hu [this message] 2012-02-02 17:04 ` tamas at eisenberger dot hu 2012-02-03 22:45 ` tamas at eisenberger dot hu 2012-02-03 22:46 ` tamas at eisenberger dot hu 2012-02-03 22:47 ` tamas at eisenberger dot hu 2012-02-07 17:07 ` tromey at redhat dot com 2012-02-16 14:36 ` cvs-commit at gcc dot gnu.org 2012-02-16 14:39 ` tromey at redhat dot com 2012-02-16 17:36 ` tamas at eisenberger dot hu
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-13653-4717-pH5GqAS56V@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).