From: "Uri Moszkowicz" <uri@4refs.com>
To: gdb@sources.redhat.com
Cc: "Nick Roberts" <nickrob@snap.net.nz>
Subject: Re: c++/2208: Checkpoints not saved on restart
Date: Wed, 10 Jan 2007 16:22:00 -0000 [thread overview]
Message-ID: <f32f8f30701100822s32c46d23i3beb88d50092748b@mail.gmail.com> (raw)
In-Reply-To: <1167813680.9414.4.camel@kahikatea.snap.net.nz>
Hi,
I submitted this bug report and am forwarding it to this list at the
request of Nick Roberts. This bug concerns checkpointing and is
probably more of a feature request than a bug (though I've submitted
several other real checkpointing bugs).
While I'm glad to have checkpointing support, its not as useful as it
may appear since you can only revert to a saved checkpoint once. After
restarting a saved checkpoint it is lost. I propose that a restart
checkpoint should first fork before execution thus allowing a user to
replay from a given checkpoint multiple times.
Checkpointing after any restart would be a temporary workaround except
for bug #2209, which states that checkpointing after restart causes a
deadlock.
Thanks,
Uri
On 1/3/07, Nick Roberts <nickrob@snap.net.nz> wrote:
> http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2208
>
> > 1. set 2 breakpoint and run to first
> > 2. "checkpoint"
> > 3. "continue"
> > 4. "restart 1"
> > 5. "continue"
> > 6. "info checkpoints"
>
> > Notice how checkpoint 1 has moved to the second breakpoint.
>
> I think that's because 5. "continue" took it there. Have you read the
> description of checkpoints in the manual? I think it's a good idea
> to post to gdb@sources.redhat.com first, and only file as a bug once
> there is agreement that it is one.
>
>
next parent reply other threads:[~2007-01-10 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1167813680.9414.4.camel@kahikatea.snap.net.nz>
2007-01-10 16:22 ` Uri Moszkowicz [this message]
2007-01-10 21:51 ` Nick Roberts
2007-01-10 21:59 ` Uri Moszkowicz
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=f32f8f30701100822s32c46d23i3beb88d50092748b@mail.gmail.com \
--to=uri@4refs.com \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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