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

[Jim Ingham <jingham@apple.com>]

Project Builder (Apple's IDE which runs on top of gdb) only sets future
breakpoints, and Insight could easily do that.

The big difference between break and future break is that if you mistype a
name in future-break, you won't get an error.  You do get some console
output telling you that it didn't work, but this is not the same in scripts,
for instance.  This is a semantic change in how break works, and for that
reason I hesitate to just convert break to future break...

What do other folks think?

Jim

> 
>>>>>> "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

-- 
+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==
Jim Ingham                              jingham@apple.com
Developer Tools - gdb