This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
- From: greenrd at greenrd dot org
- To: gdb-gnats at sources dot redhat dot com
- Date: 14 Apr 2005 16:54:10 -0000
- Subject: breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
- Reply-to: greenrd at greenrd dot org
>Number: 1917
>Category: breakpoints
>Synopsis: Setting pending breakpoints is not scriptable, at least not intuitively
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Apr 14 16:58:01 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator: greenrd@greenrd.org
>Release: 6.3.50.20050413
>Organization:
>Environment:
Fedora Core 4 test 1
>Description:
I wanted to script the setting of a pending breakpoint for another gdb bug report, but I could not work out how to do so. When gdb is used interactively, attempting to set a breakpoint on a symbol that does not yet exist will trigger the question:
Make breakpoint pending on future shared library load? (y or [n])
However, in scripting mode, this question does not occur, and there is no documented option to the b command in "help b" to do a pending breakpoint from a script.
>How-To-Repeat:
echo b bogussymbol >tempfile
/usr/src/build/gdb/gdb -x tempfile ls
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: