This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Pending breakpoints and scripts
- From: Andrew Cagney <cagney at gnu dot org>
- To: gdb at sources dot redhat dot com
- Date: Mon, 09 Feb 2004 15:02:19 -0500
- Subject: Pending breakpoints and scripts
Anyone noticed this?
(top-gdb) run testsuite/gdb.base/advance
Starting program: ...
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Breakpoint 1 (internal_error) pending.
Function "info_command" not defined.
Breakpoint 2 (info_command) pending.
(top-gdb)
It's caused by this:
if (!query ("Make breakpoint pending on future shared library
load? ")
)
return rc;
The old behavior was: when in batch mode, throw an error (and hence
abandon the script) if the breakpoint insert fails.
The new behavior is: when in batch mode, always insert the breakpoint.
when not in batch mode never throw an error.
For the existing behavior to be restored the query's logic would need to
be reversed (ask the oposite question) and then re-throw the error. A
/pending qualifier could then be added.
Thoughts?
Andrew