Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: jan.kratochvil@redhat.com, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Runtime regression for gdb.base/reread.exp & co. [Re: [RFA] Remove target_section.bfd]
Date: Mon, 22 Jul 2013 16:25:00 -0000	[thread overview]
Message-ID: <878v0y7eaw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20968.34352.845515.406613@ruffy.mtv.corp.google.com> (Doug	Evans's message of "Thu, 18 Jul 2013 17:20:00 -0700")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> The change was added here:
Doug> http://sourceware.org/ml/gdb-patches/2012-07/msg00742.html
Doug> Tom: Can you remember the reproducer for the issue fixed by this patch?

This is all I have:

    http://sourceware.org/ml/gdb-patches/2011-12/msg00493.html

Basically, I tripped across a case where gdb assumed that BFDs were not
shared.

Doug> Note that all calls to remove_target_sections pass the bfd from "key":

I didn't understand this, but reading the patch made it all clear.
It looks good to me, thanks.

Tom


  reply	other threads:[~2013-07-22 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 22:42 [RFA] Remove target_section.bfd Doug Evans
2013-07-16 18:13 ` Tom Tromey
2013-07-16 18:27   ` Doug Evans
2013-07-16 18:39     ` Tom Tromey
2013-07-17  4:33 ` Build regression with --enable-targets=all [Re: [RFA] Remove target_section.bfd] Jan Kratochvil
2013-07-17  5:31   ` Doug Evans
2013-07-18 10:54 ` Runtime regression for gdb.base/reread.exp & co. " Jan Kratochvil
2013-07-18 16:24   ` Doug Evans
2013-07-18 16:33     ` Jan Kratochvil
2013-07-19  0:20       ` Doug Evans
2013-07-22 16:25         ` Tom Tromey [this message]
2013-07-22 20:53           ` [commit] " Jan Kratochvil
2013-07-19  0:27       ` Doug Evans

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=878v0y7eaw.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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