From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: William Lee Irwin III <wli@holomorphy.com>,
"David S. Miller" <davem@redhat.com>,
frank.schafer@setuza.cz, linux-kernel@vger.kernel.org
Subject: Re: No PTRACE_READDATA for archs other than SPARC?
Date: Wed, 29 May 2002 20:15:55 -0400 [thread overview]
Message-ID: <20020530001555.GA4831@branoic.them.org> (raw)
In-Reply-To: <Pine.GSO.4.05.10205192307500.26915-100000@rain.cise.ufl.edu> <20020519.214053.19164382.davem@redhat.com> <1021876190.250.7.camel@ADMIN> <20020520.141800.52934272.davem@redhat.com> <20020529235116.GB3797@branoic.them.org> <20020530000311.GY14918@holomorphy.com>
On Wed, May 29, 2002 at 05:03:11PM -0700, William Lee Irwin III wrote:
> On Mon, May 20, 2002 at 02:18:00PM -0700, David S. Miller wrote:
> >> I can't see any reason why lack of PTRACE_READDATA prevents follow
> >> fork mode support in GDB.
>
> On Wed, May 29, 2002 at 07:51:16PM -0400, Daniel Jacobowitz wrote:
> > It doesn't. Follow-fork support is possible now, with a speed hit, but
> > I am waiting for better kernel support; it should be forthcoming with
> > the task ornament-based debugging interface proposed some time ago.
>
> What is this and who is working on it?
David Howells, at the same time as the rest of the task ornaments
stuff. You'd have to ask him what the current state of it is.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-30 0:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 3:08 No PTRACE_READDATA for archs other than SPARC? Pradeep Padala
2002-05-20 4:40 ` David S. Miller
2002-05-20 6:29 ` Frank Schaefer
2002-05-20 21:18 ` David S. Miller
2002-05-29 23:51 ` Daniel Jacobowitz
2002-05-30 0:03 ` William Lee Irwin III
2002-05-30 0:15 ` Daniel Jacobowitz [this message]
2002-05-20 20:12 ` Pradeep Padala
2002-05-29 23:49 ` Daniel Jacobowitz
2002-05-30 0:31 ` David S. Miller
2002-05-30 0:48 ` Daniel Jacobowitz
2002-05-30 15:22 ` Pradeep Padala
2002-06-04 4:37 ` David S. Miller
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=20020530001555.GA4831@branoic.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=davem@redhat.com \
--cc=frank.schafer@setuza.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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