This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] add 'save-breakpoints' command


>>>>> "Klee" == Klee Dienes <klee@apple.com> writes:

Klee> The 'future-break' command allows one to specify a breakpoint
Klee> that starts off as 'shlib_disabled' instead of generating an
Klee> error if it can't be set immediately.

Klee> I'm not entirely happy with the future-break command, and
Klee> particularly with its interaction with the save-breakpoints
Klee> mechanism (if you set a breakpoint that is in a shared library
Klee> after shared libraries have been loaded, you have to remember to
Klee> use the future-break command, not the break command).

Doesn't this mean that programs like Insight would be best advised to
*only* set future breakpoints?  In that case let's just add the
functionality directly to the existing breakpoint commands.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]