From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: michsnyd@cisco.com, gdb@sources.redhat.com, eliz@gnu.org
Subject: Re: [RFC] a prototype checkpoint-restart using core files
Date: Mon, 07 Nov 2005 20:22:00 -0000 [thread overview]
Message-ID: <200511072021.jA7KLanV015248@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20051107190724.GA19531@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 7 Nov 2005 14:07:24 -0500)
> Date: Mon, 7 Nov 2005 14:07:24 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> > If I read the code correctly, there is one rather serious limitation
> > though: restoring mmapped area's will fail if the same area isn't
> > mapped in the target process. Especially on systems that randomize
> > the location of mmapped memory this will make the usefullness of this
> > feature pretty limited :(.
>
> Why should it? The expected use is to restore these dumps into the
> same running session - just after stepping a bit. So unless you step
> across a very large free(), it should be fine.
Ah, somehow I forgar about the "same running session" part. Guess
that's one of the things that needs to be clearly documented then ;-).
Thanks Daniel,
Mark
next prev parent reply other threads:[~2005-11-07 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 1:35 Michael Snyder
2005-11-07 0:19 ` Daniel Jacobowitz
2005-11-07 4:40 ` Eli Zaretskii
2005-11-07 18:57 ` Mark Kettenis
2005-11-07 19:07 ` Daniel Jacobowitz
2005-11-07 19:50 ` Michael Snyder
2005-11-07 20:22 ` Mark Kettenis [this message]
2005-11-07 20:26 ` Daniel Jacobowitz
2005-11-07 23:56 ` Michael Snyder
2005-11-08 0:34 ` Soam Vasani
2005-11-08 0:43 ` Michael Snyder
2005-11-07 19:43 ` Michael Snyder
2005-11-07 20:56 ` Eli Zaretskii
2005-11-08 0:10 ` Michael Snyder
2005-11-16 0:37 ` Stan Shebs
2005-11-18 3:37 Michael Snyder
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=200511072021.jA7KLanV015248@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=michsnyd@cisco.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).