This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc][3/3] Remote core file generation: memory map
- From: Pedro Alves <pedro at codesourcery dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org, jan dot kratochvil at redhat dot com, sergiodj at redhat dot com
- Date: Wed, 9 Nov 2011 19:30:53 +0000
- Subject: Re: [rfc][3/3] Remote core file generation: memory map
- References: <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