From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: sergiodj@linux.vnet.ibm.com, tromey@redhat.com,
msnyder@vmware.com, mark.kettenis@xs4all.nl,
gdb-patches@sourceware.org
Subject: Re: RFC: "info proc map" for corefiles
Date: Mon, 22 Dec 2008 22:19:00 -0000 [thread overview]
Message-ID: <umyendfad.fsf@gnu.org> (raw)
In-Reply-To: <20081222202532.GA31896@caradoc.them.org>
> Date: Mon, 22 Dec 2008 15:25:32 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= <sergiodj@linux.vnet.ibm.com>,
> tromey@redhat.com, msnyder@vmware.com, mark.kettenis@xs4all.nl,
> gdb-patches@sourceware.org
>
> I wonder if we should rename or redefine "info proc". It is currently
> /proc specific, so Sergio's new work for core files doesn't belong
> there. But while it exists we can't reasonably add a separate "info
> process".
>
> Or should we fold this into "info inferior" and make it work for other
> kinds of inferiors?
I'm okay with both of these ways, but "info process" doesn't sound
like a good name for core files, IMO.
next prev parent reply other threads:[~2008-12-22 22:19 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
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 [this message]
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=umyendfad.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@vmware.com \
--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