Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] gdb1250.exp: make 'break abort' work with new pending breakpoints
Date: Mon, 09 Feb 2004 15:38:00 -0000	[thread overview]
Message-ID: <20040209153805.GA29343@nevyn.them.org> (raw)
In-Reply-To: <20040209072340.665D84B104@berman.michael-chastain.com>

On Mon, Feb 09, 2004 at 02:23:40AM -0500, Michael Chastain wrote:
> This patch enhances gdb.base/gdb1250.exp so that it works with
> the new pending-breakpoint interface.  This test wants to set a
> breakpoint on 'abort', which may be in a shared library.
> 
> Of course it still works with the old 'just quietly set the breakpoint'
> interface.
> 
> I tested on native i686-pc-linux-gnu, red hat 8.0, glibc 2.2.93-5-rh.
> I tested with gdb 6.0 and gdb HEAD, gcc 3.3.2, binutils 2.14 and
> binutils HEAD, dwarf-2 and stabs+.  All the tests PASSed in all
> configurations.
> 
> This test is sensitive to the version of binutils because binutils HEAD
> has a PLT optimization for shared library functions.

So it used to fail with binutils HEAD, right?

> 
> Okay to commit?

This I'm not so sure about.

- Should there be a version of gdb_breakpoint that answers yes to the
pending question?
- If so, should runto use it?  Or should there be a version of runto
that does?

I think the latter might be best but I don't know what to call them. 
Maybe:
  gdb_breakpoint_allow_pending
  runto_allow_pending

> 2004-02-09  Michael Chastain  <mec.gnu@mindspring.com>
> 
> 	* gdb.base/gdb1250.exp: Improve 'break abort' to work with new
> 	pending-breakpoint user interface.

Fixing this is great though!

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-09 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  7:23 Michael Elizabeth Chastain
2004-02-09 15:38 ` Daniel Jacobowitz [this message]
2004-02-09 22:05 Michael Elizabeth Chastain
2004-02-09 22:33 ` Daniel Jacobowitz
2004-02-09 22:45 Michael Elizabeth Chastain
2004-02-09 22:51 ` Daniel Jacobowitz
2004-02-09 22:55 Michael Elizabeth Chastain
2004-02-29 17:42 ` Daniel Jacobowitz
2004-03-02 15:48 Michael Elizabeth Chastain
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-24 18:42 ` Daniel Jacobowitz

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=20040209153805.GA29343@nevyn.them.org \
    --to=drow@mvista.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