Re: Make breakpoint pending

[Keith Seitz <keiths@redhat.com>]

Guillaume Savaton wrote:
> Hi,
> 
> I have been using previous versions of insight (5.x) for a while, and I 
> have
> noticed a new message in 6.4 when I attempt to run a program :
> "Make breakpoint pending on future shared library load?"

Yeah, that happens when gdb is asked to set a breakpoint someplace that 
it knows nothing about (so it assumes that you have not made a mistake 
but that the location exists in a shared library).

> This message is quite annoying since I am asked to confirm for each 
> breakpoint
> in my program individually.

Okay, I have not seen this before, and I cannot reproduce it with any 
testcase I've managed to devise. If you look at the breakpoints which 
were marked pending, are they part of your program? [While testing this, 
I just ran into a problem where I was running in the build directory. 
Insight added the breakpoints from .gdbinit to its list of installed 
breakpoints for the executable. Those buggers just coming out of the 
woodwork!]

> Is there a possibility to tell insight not to ask ?

Yes, you can add it to the ignored warnings list or teach insight that 
it is an ignorable warning (so it will only ask once). See 
gdbtk_tcl_warning in interface.tcl to globally ignore the warning. 
Unfortunately, teaching insight to optionally ignore the warning, i.e., 
"Don't show me this warning again", is slightly non-trivial (or at least 
more painful). GDB never did clean up the warning/error landscape. All 
we know is that it is a warning.

Ignoring gdb, we'd have to add logic in place (similar to 
gdbtk_tcl_warning) to flag warnings are optionally ignorable. [Gdb just 
still doesn't get it.]

Keith