From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] checkpoint / restart, and multi-fork debugging
Date: Mon, 12 Dec 2005 23:32:00 -0000 [thread overview]
Message-ID: <uirtwd274.fsf@gnu.org> (raw)
In-Reply-To: <439A2F7D.5030503@redhat.com> (message from Michael Snyder on Fri, 09 Dec 2005 17:29:33 -0800)
> Date: Fri, 09 Dec 2005 17:29:33 -0800
> From: Michael Snyder <msnyder@redhat.com>
> CC: gdb-patches@sources.redhat.com
>
> > Finally, it would be nice to have a short description of the Linux
> > implementation of these two features in gdbint.texinfo.
>
> Where might that go, and what might it look like?
It could go into a subsection of "Algorithms", or it could be a
separate chapter (in the top-level menu).
prev parent reply other threads:[~2005-12-10 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 15:11 Michael Snyder
2005-12-09 14:23 ` Tom Tromey
2005-12-09 19:51 ` Eli Zaretskii
2005-12-09 20:59 ` Daniel Jacobowitz
2005-12-10 9:06 ` Michael Snyder
2005-12-10 9:57 ` Daniel Jacobowitz
2005-12-13 6:17 ` Eli Zaretskii
2005-12-10 7:24 ` Michael Snyder
2005-12-09 19:36 ` Eli Zaretskii
2005-12-10 8:59 ` Michael Snyder
2005-12-12 23:32 ` Eli Zaretskii [this message]
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=uirtwd274.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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