Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: michsnyd@cisco.com
Cc: gdb@sources.redhat.com, eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFC] a prototype checkpoint-restart using core files
Date: Mon, 07 Nov 2005 19:43:00 -0000	[thread overview]
Message-ID: <200511071857.jA7IvP4K005599@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <u64r5f4uh.fsf@gnu.org> (message from Eli Zaretskii on Mon, 07 Nov 2005 06:40:22 +0200)

> Date: Mon, 07 Nov 2005 06:40:22 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Date: Sun, 6 Nov 2005 19:19:37 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
> > 
> > I've got to say that this is amazingly cool.
> > 
> > Afraid that's all the comments I have time for at the moment :-)
> 
> I agree, and I'd add that getting this into GDB soon would be good.

Heh, I'd expected Eli to ask for documentation ;-)

Anyway, in this cause I think that's important since I expect a lot of
users won't understand its limitations.

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 :(.

Mark


  reply	other threads:[~2005-11-07 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  1:55 Michael Snyder
2005-11-07  4:01 ` Daniel Jacobowitz
2005-11-07 14:57   ` Eli Zaretskii
2005-11-07 19:43     ` Mark Kettenis [this message]
2005-11-07 19:50       ` Daniel Jacobowitz
2005-11-07 20:56         ` Michael Snyder
2005-11-07 20:43       ` Michael Snyder
2005-11-07 22:07       ` Eli Zaretskii
2005-11-08  6:05         ` Michael Snyder
2005-11-18  8:18 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=200511071857.jA7IvP4K005599@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --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