public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Lacage <mathieu.lacage@gmail.com>
To: gdb@sourceware.org
Subject: Re: gdb crash: double free with free_objfile
Date: Tue, 29 Jun 2010 11:57:00 -0000	[thread overview]
Message-ID: <AANLkTikW85waYHgS5qSzTUxMlo3noVKcHOB6Lrb7q-rg@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimzl4KmA-bnXnLTnANEjmPG2CE7t06ggyi3ReV_@mail.gmail.com>

I attached a reduced testcase and this patch to:
http://sourceware.org/bugzilla/show_bug.cgi?id=11766

enjoy !
Mathieu

On Wed, Jun 23, 2010 at 5:15 PM, Mathieu Lacage
<mathieu.lacage@gmail.com> wrote:
> hi,
>
> On Fri, Feb 5, 2010 at 5:39 PM, Tom Tromey <tromey@redhat.com> wrote:
>
>> Nope, right now objfile has the base address baked in to many things,
>> e.g. symbol addresses or psymtabs_addrmap.  I think we'd like to change
>> this, so that we can share objfiles between inferiors, but nobody has
>> tried to do that yet.  I don't know how hard this would be.
>>
>> Your quickest route is probably a form of (a) -- change symbol_add_stub
>> to check both the file name and the base address.
>
> It took me a long time to get back to this issue because I was busy
> with a couple of other things but the attached patch which was
> generated against CVS HEAD fixes the problem for me (i.e., avoids the
> segfault in gdb and gets me readable backtraces). Is there something
> else I could do to help get this issue fixed in mainline ?
>
> Mathieu
> --
> Mathieu Lacage <mathieu.lacage@gmail.com>
>



-- 
Mathieu Lacage <mathieu.lacage@gmail.com>

      reply	other threads:[~2010-06-29 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 12:23 Mathieu Lacage
2010-02-05 15:40 ` Tom Tromey
2010-06-23 15:15   ` Mathieu Lacage
2010-06-29 11:57     ` Mathieu Lacage [this message]

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=AANLkTikW85waYHgS5qSzTUxMlo3noVKcHOB6Lrb7q-rg@mail.gmail.com \
    --to=mathieu.lacage@gmail.com \
    --cc=gdb@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).