From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] gdb1250.exp: Handle pending breakpoint in shared library
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040311015210.GB17829@nevyn.them.org> (raw)
Message-ID: <20040319000900.Fy1HeLreMO0-OEBLwVqD9Gst-nYcV8xSgF7jhn0wULM@z> (raw)
In-Reply-To: <20040311012236.ABDC44B104@berman.michael-chastain.com>
On Wed, Mar 10, 2004 at 08:22:36PM -0500, Michael Chastain wrote:
> Here is another attempt to fix gdb1250.exp so that it works with
> the new 'pending breakpoint' feature.
>
> I would like to get this fixed so that I can take it off my list
> of regressions for binutils binutils-2_15-branch versus binutils 2.14.
>
> Tested on: native i686-pc-linux-gnu, gcc 2.95.3 3.3.3 HEAD,
> binutils 2.14 binutils-2_15-branch HEAD, dwarf-2 stabs+.
>
> I'm not sure that "run" is the right command to issue to start
> running the inferior. If it's not the right command, I would be
> happy to change it.
>
> Okay to commit?
I'd rather not. You were happy with my last patch to add runto
{allow-pending}, yes? I could just commit that.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-11 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-11 1:22 ` Michael Elizabeth Chastain
2004-03-11 1:52 ` Daniel Jacobowitz [this message]
2004-03-19 0:09 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-03-24 18:25 Michael Elizabeth Chastain
2004-03-24 18:42 ` Daniel Jacobowitz
2004-03-11 1:55 Michael Elizabeth Chastain
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-23 23:06 ` Andrew Cagney
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=20040311015210.GB17829@nevyn.them.org \
--to=drow@false.org \
--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