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 gdb/13619] Crash when running binary a second time in the same session Date: Tue, 07 Feb 2012 16:04:00 -0000 [thread overview] Message-ID: <bug-13619-4717-kqACtCkPkV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13619-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13619 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-02-07 16:03:34 UTC --- You may need to rebuild gdb without optimization to see which free is really failing. In 7.4, line 597 of objfiles.c isn't a direct call to free: gdb_bfd_unref (objfile->obfd); -- 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-07 16:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 17:53 [Bug gdb/13619] New: " hyrum at hyrumwright dot org 2012-01-24 18:40 ` [Bug gdb/13619] " hyrum at hyrumwright dot org 2012-02-07 16:04 ` tromey at redhat dot com [this message] 2012-02-07 18:20 ` hyrum at hyrumwright dot org 2012-02-07 19:29 ` tromey at redhat dot com 2012-02-07 19:44 ` hyrum at hyrumwright dot org 2012-02-07 21:16 ` tromey at redhat dot com 2012-02-08 15:14 ` tromey at redhat dot com 2012-02-08 16:16 ` hyrum at hyrumwright dot org 2012-02-08 16:21 ` tromey 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=bug-13619-4717-kqACtCkPkV@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).