This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 14 Apr 2005 17:08:00 -0000
- Subject: Re: breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR breakpoints/1917; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: greenrd@greenrd.org
Cc: gdb-gnats@sources.redhat.com
Subject: Re: breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
Date: Thu, 14 Apr 2005 13:05:20 -0400
On Thu, Apr 14, 2005 at 04:54:10PM -0000, greenrd@greenrd.org wrote:
> 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.
Take a look at the documentation of the "set breakpoint pending"
command.
--
Daniel Jacobowitz
CodeSourcery, LLC