From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>,
"tromey@redhat.com" <tromey@redhat.com>,
"mark.kettenis@xs4all.nl" <mark.kettenis@xs4all.nl>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: "info proc map" for corefiles
Date: Fri, 19 Dec 2008 19:46:00 -0000 [thread overview]
Message-ID: <494BF8A2.4030104@vmware.com> (raw)
In-Reply-To: <uocz8dkjp.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@linux.vnet.ibm.com>
>> Cc: Michael Snyder <msnyder@vmware.com>, Mark Kettenis <mark.kettenis@xs4all.nl>, "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>> Date: Fri, 19 Dec 2008 14:23:53 -0200
>>
>> Hey Tom,
>>
>> IIUC we are creating this new command because "info proc" was initially
>> designed to provide information about a live process, right?
>
> No, "info proc" was designed to provide information recorded about a
> process in the /proc filesystem. And a process that is dead does not
> have any information about it in /proc.
Oh yeah, I guess that's right. "info proc" first appeared
in solaris-gdb, and then the other hosts that shared procfs.c
(like Irix, I think) -- and then eventually appeared in
linux gdb (although /proc in linux doesn't remotely resemble
/proc everywhere else).
Are there any other gdb configs where the command appears?
That is, other than linux and systems that use procfs.c?
next prev parent reply other threads:[~2008-12-19 19:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 17:19 Sérgio Durigan Júnior
2008-12-18 18:47 ` Mark Kettenis
2008-12-18 18:51 ` Sérgio Durigan Júnior
2008-12-18 21:44 ` Michael Snyder
2008-12-19 15:54 ` Sérgio Durigan Júnior
2008-12-19 16:04 ` Mark Kettenis
2008-12-19 16:06 ` Tom Tromey
2008-12-19 16:24 ` Sérgio Durigan Júnior
2008-12-19 19:37 ` Eli Zaretskii
2008-12-19 19:46 ` Michael Snyder [this message]
2008-12-22 15:35 ` Sérgio Durigan Júnior
2008-12-22 16:28 ` Tom Tromey
2008-12-22 19:37 ` Eli Zaretskii
2008-12-22 19:55 ` Sérgio Durigan Júnior
2008-12-22 20:04 ` Eli Zaretskii
2008-12-22 20:26 ` Daniel Jacobowitz
2008-12-22 22:19 ` Eli Zaretskii
2008-12-22 22:52 ` Mark Kettenis
2008-12-29 19:56 ` Sérgio Durigan Júnior
2008-12-19 16:25 ` Eli Zaretskii
2008-12-19 18:09 ` Sérgio Durigan Júnior
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=494BF8A2.4030104@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=sergiodj@linux.vnet.ibm.com \
--cc=tromey@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