Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: implement 'info proc mappings' for core files
Date: Mon, 05 Nov 2012 21:48:00 -0000	[thread overview]
Message-ID: <877gpzloii.fsf@fleche.redhat.com> (raw)
In-Reply-To: <871ug8nnqw.fsf__31325.5512774505$1352124723$gmane$org@fleche.redhat.com>	(Tom Tromey's message of "Mon, 05 Nov 2012 07:11:19 -0700")

Sergio> Wow, I totally forgot about this feature.  In fact, I thought Ulrich's
Sergio> patch had already implemented it!  If I knew it hadn't been implemented,
Sergio> I would have sent my patches again :-).  Shame on me.

Tom> I totally forgot there were patches in this area, too :(
Tom> I will dig them up and look at them.

Well, ouch.  Here are the threads I found

http://sourceware.org/ml/gdb-patches/2008-12/msg00322.html
http://sourceware.org/ml/gdb-patches/2011-11/msg00101.html
http://sourceware.org/ml/gdb-patches/2011-12/msg00018.html

If you look through the monthly archives there are some detached
sub-threads as well.

I found it pretty hard to find the conclusion.  IIUC what actually went
in was a patch to have gdbserver read the remote /proc entries and serve
them up verbatim, for parsing locally.

For those opposed to "info proc" working on core files, if you are still
opposed, let me know.  I guess I can resurrect Sergio's "info core"
command.

Tom


  parent reply	other threads:[~2012-11-05 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 18:42 Tom Tromey
2012-11-03  3:45 ` Sergio Durigan Junior
     [not found] ` <m3vcdnjqn5.fsf__5583.70666481114$1351914377$gmane$org@redhat.com>
2012-11-05 14:11   ` Tom Tromey
     [not found]   ` <871ug8nnqw.fsf__31325.5512774505$1352124723$gmane$org@fleche.redhat.com>
2012-11-05 21:48     ` Tom Tromey [this message]
2012-11-20 20:05       ` Tom Tromey
2012-11-20 20:16         ` Eli Zaretskii
2012-12-03  9:29         ` Jan Kratochvil
2012-12-03 17:26           ` Tom Tromey
2012-12-14 15:17             ` Tom Tromey

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=877gpzloii.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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