From: Daniel Jacobowitz <drow@mvista.com>
To: Charles James Leonardo Quarra Cappiello <charsquarra@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: questions / suggestions about gdb
Date: Tue, 07 May 2002 13:03:00 -0000 [thread overview]
Message-ID: <20020507200317.GA28606@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-05-07 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 12:06 Charles James Leonardo Quarra Cappiello
2002-05-07 13:03 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 6:55 Charles James Leonardo Quarra Cappiello
2002-05-08 5:48 Michael Elizabeth Chastain
2002-05-08 6:47 ` Eli Zaretskii
2002-05-08 6:58 ` Petr Sorfa
2002-05-08 6:53 ` Petr Sorfa
2002-05-07 15:18 Charles James Leonardo Quarra Cappiello
2002-05-07 13:36 Charles James Leonardo Quarra Cappiello
2002-05-07 15:02 ` Andrew Cagney
2002-05-07 11:58 Charles James Leonardo Quarra Cappiello
2002-05-07 12:00 ` Daniel Jacobowitz
2002-05-07 12:22 ` William A. Gatliff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020507200317.GA28606@nevyn.them.org \
--to=drow@mvista.com \
--cc=charsquarra@hotmail.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox