public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "davidbalbert at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14290] gdb_bfd_unref frees an already freed memory block Date: Tue, 27 Nov 2012 17:39:00 -0000 [thread overview] Message-ID: <bug-14290-4717-tvZOICzFni@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14290-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14290 --- Comment #9 from David Albert <davidbalbert at gmail dot com> 2012-11-27 17:39:22 UTC --- The patch works for me (I applied it on top of the latest trunk). One question: on line 94 of the patch, is it necessary to call gdb_bfd_ref on `result`? In this case, bfd_mach_o_fat_extract was basically a noop, and `abfd` was already reference counted by solib_bfd_open. -- 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-11-27 17:39 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-24 23:50 [Bug gdb/14290] New: " johnw at boostpro dot com 2012-06-24 23:51 ` [Bug gdb/14290] " johnw at boostpro dot com 2012-07-31 4:47 ` tromey at redhat dot com 2012-11-19 4:43 ` davidbalbert at gmail dot com 2012-11-19 14:55 ` tromey at redhat dot com 2012-11-22 2:46 ` davidbalbert at gmail dot com 2012-11-22 2:47 ` davidbalbert at gmail dot com 2012-11-27 15:47 ` tromey at redhat dot com 2012-11-27 15:49 ` tromey at redhat dot com 2012-11-27 17:39 ` davidbalbert at gmail dot com [this message] 2012-11-27 17:46 ` tromey at redhat dot com 2012-11-27 17:47 ` tromey at redhat dot com 2012-11-27 19:28 ` davidbalbert at gmail dot com 2012-11-28 18:48 ` cvs-commit at gcc dot gnu.org 2012-11-28 18:50 ` tromey at redhat dot com 2012-11-28 19:36 ` davidbalbert at gmail dot com 2012-11-28 20:22 ` 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-14290-4717-tvZOICzFni@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).