This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: questions / suggestions about gdb
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Charles James Leonardo Quarra Cappiello <charsquarra at hotmail dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 7 May 2002 16:03:17 -0400
- Subject: Re: questions / suggestions about gdb
- References: <F120Vn2AI3F5Y0ZwBt30000d437@hotmail.com>
On Tue, May 07, 2002 at 03:06:57PM -0400, Charles James Leonardo Quarra Cappiello wrote:
>
>
> On Tue, 7 May 2002 15:00:37 -0400 Daniel Jacobowitz wrote:
>
> >On Tue, May 07, 2002 at 02:58:03PM -0400, Charles James Leonardo Quarra
> >Cappiello wrote:
> >> Hi,
> >>
> >>
> >> I'm an often user of gdb, and i was wondering, since debuggers cant go
> >to
> >> past states (no inversibility of the run), it would be nice if two
> >> instances of the debugger could run synchronized with a given step
> >offset,
> >> so when the advanced instance break, the retarded instance stops,
> >keeping
> >> an analogous state which can be studied.
> >>
> >> This actually can be done or is not feasible? If can't be done just now
> >but
> >> is from the debugger's developers point of view feasible, consider this
> >a
> >> feature request.
> >
> >GDB just gained a feature that'll do almost what you want: the
> >`generate-core-file' command. You can then debug the new corefile to
> >examine the frozen state.
> >
> can i activate the 'generate-core-file' a few steps before the program
> breaks?
Whenever you want to; you just issue the command, and then you can come
back to look at the core file later.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer