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

Daniel Jacobowitz
2001-12-04T18:26:52Z

On Tue, Dec 04, 2001 at 01:21:25PM -0500, Klee Dienes wrote:
>
> For a long time, we (the folks at Apple), have been wanting to unify
> our source tree with the Cygnus GDB source tree, for all the
> free-software reasons I'm sure I don't need enumerate.
>
> Over the past couple of years, we managed to bring our source tree
> up-to-date with respect the current Cygnus tree (it used to be based
> off of gdb-4.14), executed a copyright assignment, and made a massive
> diff available, but the actual work of pushing our changes back to
> Cygnus (cleanly and as individual patch files) has always been
> prioritized just under "make GDB work well on our platform."
>
> Thankfully, GDB now works pretty well on our platform, so we're
> finally getting the time to do the work of merging our changes back
> into the Cygnus tree.
>
> We've got a ton of stuff to submit, but as a warm-up, I'm starting
> witha relatively minor feature-addition --- a command to save the
> current set of breakpoints to a file that can be read in later. We've
> been using this on our platform for a few months now, and folks seem
> to like it. I've also tested the patch against the i386/Linux
> testsuite ... nothing appears to break.

Disclaimer: I haven't actually read through the patch yet, but the
changelog doesn't seem to mention this. This is more of a comment to
the list than a comment on the patch.

Do you address the issue of breakpoints which can not be set at a
particular time? For instance, breakpoints in dlopen()'d modules can
not be reset at the start of the next session.

I'm going to guess that that's out of scope for this patch, but it's
just a flag on my todo list. It'd be nice to be able to set a
breakpoint even if the symbol isn't immediately resolvable, without
breaking error reporting completely.

--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer