Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: sergiodj@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: "info proc map" for corefiles
Date: Thu, 18 Dec 2008 18:47:00 -0000	[thread overview]
Message-ID: <200812181846.mBIIkTgK015985@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <1229620702.6602.12.camel@miki> (message from 	=?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= on Thu, 18 	Dec 2008 15:18:22 -0200)

> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@linux.vnet.ibm.com>
> Date: Thu, 18 Dec 2008 15:18:22 -0200
> 
> Hi guys and girls,
> 
> This little patch o' mine implements the command "info proc map" for
> corefiles in GDB. Initially, this feature is only provided for live
> process being debugged. We decided that it would be good to have such
> functionality for corefiles as well, since this information (the memory
> mappings) is available inside them.
> 
> This was something that Thiago and I have discussed for some time, and
> it took a little while for me to figure out how things worked in this
> part of the code. I really don't know if this is the right way to
> implement this, so I'd be glad if you could take a look and give your
> opinions.
> 
> It's not architecture-dependend so this time you'll be able to test
> without problems. Comments and reviews are welcome, as always.

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.


  reply	other threads:[~2008-12-18 18:47 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 [this message]
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
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=200812181846.mBIIkTgK015985@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --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