From: Daniel Jacobowitz <drow@mvista.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: question about GDB, ptrace, and /proc...
Date: Sat, 10 Jan 2004 06:52:00 -0000 [thread overview]
Message-ID: <20040110065215.GA31344@nevyn.them.org> (raw)
In-Reply-To: <20040110055300.GV4978@gnat.com>
On Sat, Jan 10, 2004 at 09:53:00AM +0400, Joel Brobecker wrote:
> Hello,
>
> while reading some linux-specific code such as linux-nat.c for instance,
> I was a bit surprised to see some calls to functions which seem to use
> /proc. For instance, there is a call to child_pid_to_exec_file() inside
> linux_handle_extended_wait() in linux-nat.c which causes GDB to read
> into the /proc filesystem.
>
> I was surprised, because I thought the linux ports were using ptrace,
> meaning using ptrace exclusively. Does GDB also need /proc, or is /proc
> only optional? Or does GDB support both interfaces on Linux?
The Linux /proc filesystem is not at all like the Solaris-style /proc.
It can not be used as a replacement for ptrace. However, for some
things (like child_pid_to_exec_file) it's the only option. And for
others (lin_lwp_xfer_memory) it's dramatically more efficient.
Right now, GDB will behave gracefully if /proc is unavailable, for most
uses. However I wouldn't consider that a guarantee if I were you. As
time goes by more and more Linux userspace functionality relies on
/proc.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-01-10 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 5:53 Joel Brobecker
2004-01-10 6:52 ` Daniel Jacobowitz [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=20040110065215.GA31344@nevyn.them.org \
--to=drow@mvista.com \
--cc=brobecker@gnat.com \
--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