From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, 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 22:05:00 -0000 [thread overview]
Message-ID: <20040209220529.43B094B363@berman.michael-chastain.com> (raw)
mec> This test is sensitive to the version of binutils because binutils HEAD
mec> has a PLT optimization for shared library functions.
drow> So it used to fail with binutils HEAD, right?
"Used to" as in "has been failing since 2003-11-27 to 2004-02-09", yes.
It was pr gdb/1470. Maybe it slipped off your radar screen.
> - 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?
Err, yeah. I suppose the right thing is to make
gdb_breakpoint_with_pending $name $pendingp
Then:
proc gdb_breakpoint { name } {
return gdb_breakpoint_with_pending "$name" "no"
}
I see 3 instance of "gdb_breakpoint exit" and they need to be
investigated.
On principle, same with "runto".
I don't know what the right name is, either. But I do think that the
the new functions should take a second parameter.
Michael C
next reply other threads:[~2004-02-09 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 22:05 Michael Elizabeth Chastain [this message]
2004-02-09 22:33 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 15:48 Michael Elizabeth Chastain
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-24 18:42 ` Daniel Jacobowitz
2004-02-09 22:55 Michael Elizabeth Chastain
2004-02-29 17:42 ` Daniel Jacobowitz
2004-02-09 22:45 Michael Elizabeth Chastain
2004-02-09 22:51 ` Daniel Jacobowitz
2004-02-09 7:23 Michael Elizabeth Chastain
2004-02-09 15:38 ` 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=20040209220529.43B094B363@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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