Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com,
	sergiodj@redhat.com
Subject: Re: [rfc][3/3] Remote core file generation: memory map
Date: Wed, 09 Nov 2011 19:31:00 -0000	[thread overview]
Message-ID: <201111091930.53937.pedro@codesourcery.com> (raw)
In-Reply-To: <201111091827.pA9IR7UH023183@d06av02.portsmouth.uk.ibm.com>

On Wednesday 09 November 2011 18:27:07, Ulrich Weigand wrote:

> OK.  In the meantime, I've noticed the discussion going on in parallel
> on the "info core mappings" commands.  If we implement this, we have
> the somewhat weird situation that we can show mappings for native
> processes and for core files, but not for processes attached to remotely,
> even if the target is also Linux ...
> 
> It would appear to me that this command actually just needs the very
> same data I need here for the generate-core-file command, namely the
> current list of memory mappings.
> 
> If we create a new target object for VMA memory mappings, maybe we
> ought to then have a standard "info mappings" (or the like) command
> implemented in GDB *common code* that works likewise on native,
> core file, *and* also gdbserver targets; in fact, on all targets
> that provide that new target object (which may need to be a bit
> richer, e.g. provide mapped file names as well)?

Sounds like a good idea indeed.

-- 
Pedro Alves


  reply	other threads:[~2011-11-09 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 19:54 Ulrich Weigand
2011-11-01 18:41 ` Jan Kratochvil
2011-11-01 21:28   ` Ulrich Weigand
2011-11-08 17:25     ` Ulrich Weigand
2011-11-09 16:37       ` Pedro Alves
2011-11-09 18:27         ` Ulrich Weigand
2011-11-09 19:31           ` Pedro Alves [this message]
2011-11-09 20:04             ` Sergio Durigan Junior

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=201111091930.53937.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=sergiodj@redhat.com \
    --cc=uweigand@de.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