From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14255 invoked by alias); 9 Nov 2011 19:31:13 -0000 Received: (qmail 14166 invoked by uid 22791); 9 Nov 2011 19:31:12 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 Nov 2011 19:30:59 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RODrO-0001oe-8n from pedro_alves@mentor.com ; Wed, 09 Nov 2011 11:30:58 -0800 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Nov 2011 19:30:55 +0000 From: Pedro Alves To: "Ulrich Weigand" Subject: Re: [rfc][3/3] Remote core file generation: memory map Date: Wed, 09 Nov 2011 19:31:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-12-generic; KDE/4.7.2; x86_64; ; ) Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com, sergiodj@redhat.com References: <201111091827.pA9IR7UH023183@d06av02.portsmouth.uk.ibm.com> In-Reply-To: <201111091827.pA9IR7UH023183@d06av02.portsmouth.uk.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111091930.53937.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00256.txt.bz2 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