From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Build inf-ptrace.o when ptrace available
Date: Mon, 04 Oct 2004 18:23:00 -0000 [thread overview]
Message-ID: <200410041823.i94INsMM001356@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41618D95.2050003@gnu.org> (message from Andrew Cagney on Mon, 04 Oct 2004 13:51:17 -0400)
Date: Mon, 04 Oct 2004 13:51:17 -0400
From: Andrew Cagney <cagney@gnu.org>
> Going forward we need to get GNU/Linux and other systems using procfs
> and an obvious migration path for that is to build support for both
> procfs and ptrace into a single GDB. The default being to use ptrace.
>
> The /proc on Linux is not even close to a "real" procfs.
Fortunatly, that can be fixed (just like any other kernel bug - we've
been seeing success in that area recently ;-).
You know Andrew, you can be really funny ;-).
Mark
next prev parent reply other threads:[~2004-10-04 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 20:40 Andrew Cagney
2004-10-01 21:54 ` Mark Kettenis
2004-10-04 14:24 ` Andrew Cagney
2004-10-04 14:34 ` Daniel Jacobowitz
2004-10-04 16:27 ` Andrew Cagney
2004-10-04 16:35 ` Daniel Jacobowitz
2004-10-05 22:44 ` Andrew Cagney
2004-10-05 22:59 ` Daniel Jacobowitz
2004-10-05 23:42 ` Andrew Cagney
2004-10-11 17:24 ` Andrew Cagney
2004-10-13 13:54 ` Daniel Jacobowitz
2004-10-14 17:14 ` Mark Kettenis
2004-10-04 17:20 ` Mark Kettenis
2004-10-04 17:51 ` Andrew Cagney
2004-10-04 18:23 ` Mark Kettenis [this message]
2004-10-03 14:50 ` Daniel Jacobowitz
2004-10-04 14:31 ` Andrew Cagney
2004-10-04 14:34 ` Daniel Jacobowitz
2004-10-04 16:18 ` Andrew Cagney
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=200410041823.i94INsMM001356@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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