This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] checkpoint / restart, and multi-fork debugging
- From: Eli Zaretskii <eliz at gnu dot org>
- To: tromey at redhat dot com
- Cc: msnyder at redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Fri, 09 Dec 2005 16:23:34 +0200
- Subject: Re: [RFA] checkpoint / restart, and multi-fork debugging
- References: <439614B1.2030206@redhat.com> <m3bqzqwvjy.fsf@localhost.localdomain>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Cc: gdb-patches@sources.redhat.com
> From: Tom Tromey <tromey@redhat.com>
> Date: 09 Dec 2005 00:58:57 -0700
>
> One thing I didn't see mentioned in the docs is the effect on gdb of a
> 'restart'. I assume that new breakpoints, watchpoints, etc, are kept
> instead of reverting to the state at the checkpoint. Maybe this is
> worth mentioning.
I agree this is worth mentioning.
> A nice problem this solves is handling watchpoints when the system has
> address space randomization. I run into this all the time when
> debugging -- back before this feature was added to the OS I would put
> a fair amount of effort into finding some address to watch in one
> debug session, then restart the inferior with a watchpoint set.
> Randomization made this impossible; but with this patch I could just
> make a checkpoint at 'main'.
Perhaps we should mention this as well.