From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6694 invoked by alias); 7 Jun 2008 20:01:35 -0000 Received: (qmail 6686 invoked by uid 22791); 7 Jun 2008 20:01:34 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.241) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 07 Jun 2008 20:01:14 +0000 Received: by rv-out-0708.google.com with SMTP id b17so1537770rvf.48 for ; Sat, 07 Jun 2008 13:01:13 -0700 (PDT) Received: by 10.141.106.14 with SMTP id i14mr965842rvm.178.1212868873293; Sat, 07 Jun 2008 13:01:13 -0700 (PDT) Received: from ?192.168.1.102? ( [75.0.178.24]) by mx.google.com with ESMTPS id b39sm9583093rvf.8.2008.06.07.13.01.11 (version=SSLv3 cipher=RC4-MD5); Sat, 07 Jun 2008 13:01:11 -0700 (PDT) To: Andreas Schwab Subject: Re: How can I get a memory map out of a core file? Date: Sat, 07 Jun 2008 20:01:00 -0000 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: gdb@sourceware.org, Eli Zaretskii , Michael Snyder References: <668c430c0806061345m3c480d95nac5d19b02998715c@mail.gmail.com> <484AD008.8845E46E@dessent.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806071301.09679.Bruce.Korb@gmail.com> From: Bruce Korb Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00050.txt.bz2 On Saturday 07 June 2008 11:28:55 am Andreas Schwab wrote: > Brian Dessent writes: > > > Local core dump file: > > `/home/brian/core', file type elf32-i386. > > 0x08054000 - 0x08055000 is load2 > > 0x08055000 - 0x08058000 is load3 > > 0x40016000 - 0x40017000 is load5 > > 0xbffff000 - 0xc0000000 is load6 > > 0xffffe000 - 0xfffff000 is load7 > > > > Though I suppose those section names are not really all that useful, > > Those are not sections (a corefile does not contain any sections), but > segments (which are unnamed). And are what I was looking for. "info target" just wasn't jumping out as the way to get the list of mapped data. The list is a little weird with zero length sections, but I can tell what's mapped now. Thank you!! Perhaps put "memory map" in the index and point to "info target"? I went for that phrase due to the well-known "pmap": NAME pmap - display information about process memory mappings SYNOPSIS pmap [ -d | -q | -h | -V ] pid DESCRIPTION pmap(1) displays information about a process's memory mappings, such as its stack, data segment, mapped files, and so on. Thank you for your help! Regards, Bruce