This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa/testsuite] gdb1250.exp: make 'break abort' work with new pending breakpoints
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: drow at mvista dot com, mec dot gnu at mindspring dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 9 Feb 2004 17:05:29 -0500 (EST)
- Subject: Re: [rfa/testsuite] gdb1250.exp: make 'break abort' work with new pending breakpoints
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