Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: tromey@redhat.com
Cc: Michael Snyder <msnyder@vmware.com>,
	        Mark Kettenis <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 16:24:00 -0000	[thread overview]
Message-ID: <1229703833.6602.28.camel@miki> (raw)
In-Reply-To: <m3prjoi20v.fsf@fleche.redhat.com>

Hey Tom,

On Fri, 2008-12-19 at 09:05 -0700, Tom Tromey wrote:
> I agree that "info proc" a misnomer.  But, it seems to me it would be
> nice for the user to use the same command in both cases.  How about a
> new command (not "info core"), with the old "info proc map" aliased to
> it?

IIUC we are creating this new command because "info proc" was initially
designed to provide information about a live process, right? So what if
we change the "design assumptions" of it? What if "info proc" could be
used to display info about a process, whether it's running or not?

Ok, just in case you don't agree with what I proposed above, what do you
think if this new command (to which "info proc map" would be aliased) to
be called "info mapping"? Don't know if it's a good name, but I tried to
make it represent both "info proc map" and "info core map" :-).

Regards,

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil


  reply	other threads:[~2008-12-19 16:24 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 [this message]
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
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=1229703833.6602.28.camel@miki \
    --to=sergiodj@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@vmware.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