Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: fnf@redhat.com
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix gdb.base/gdb1250.exp to work when abort() is in a shared library
Date: Mon, 23 Feb 2004 13:57:00 -0000	[thread overview]
Message-ID: <20040223135711.GA28393@nevyn.them.org> (raw)
In-Reply-To: <200402222326.33562.fnf@ninemoons.com>

On Sun, Feb 22, 2004 at 11:26:33PM -0700, Fred Fish wrote:
> On Sunday 22 February 2004 23:04, Michael Elizabeth Chastain wrote:
> > On native i686-pc-linux-gnu, this used to work and then stopped
> > working with a PLT optimization in binutils HEAD.
> 
> Thanks for the history on why this doesn't currently work.  Most of my
> shared library work with gdb was from way back in the days when I'm
> pretty sure that you couldn't set breakpoints on symbols in shared
> libraries that had not yet been loaded, but perhaps I'm
> misremembering.
> 
> Perhaps it would make sense to go ahead and install this change and
> then have a separate test that specifically checks that gdb can set a
> breakpoint on symbols expected to be in a shared library.

I believe that Jeff submitted a patch to use pending breakpoints in
this test, which also fixes the issue.  Did that get lost?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-23 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  6:04 Michael Elizabeth Chastain
2004-02-23  6:26 ` Fred Fish
2004-02-23 13:57   ` Daniel Jacobowitz [this message]
2004-02-23 13:58   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23  5:57 Fred Fish

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=20040223135711.GA28393@nevyn.them.org \
    --to=drow@false.org \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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