Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: "info proc map" for corefiles
Date: Thu, 18 Dec 2008 21:44:00 -0000	[thread overview]
Message-ID: <494AC2D3.9090705@vmware.com> (raw)
In-Reply-To: <1229626216.6602.15.camel@miki>

Sérgio Durigan Júnior wrote:
> Hello Mark,
> 
> On Thu, 2008-12-18 at 19:46 +0100, Mark Kettenis wrote:
> 
>> This looks pretty cool, but I think having this as "info proc"
>> subcommand is wrong:
>>
>> (gdb) help info
>> ...
>> info proc -- Show /proc process information about any running process
>> ...
>>
>> Corefiles have nothing to do with /proc and many operating systems
>> don't even have such a thing.
> 
> All right, good point. Do you have any suggestion for this? Should I
> create another class of command?

"info core"?

There are probably a bunch of things we could expose about a
core file that would not make sense for a process, and vice versa.


  reply	other threads:[~2008-12-18 21:44 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 [this message]
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
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=494AC2D3.9090705@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=sergiodj@linux.vnet.ibm.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