From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21322 invoked by alias); 9 Jun 2008 17:52:02 -0000 Received: (qmail 21313 invoked by uid 22791); 9 Jun 2008 17:52:01 -0000 X-Spam-Check-By: sourceware.org Received: from mtagate4.de.ibm.com (HELO mtagate4.de.ibm.com) (195.212.29.153) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 09 Jun 2008 17:51:41 +0000 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.13.8/8.13.8) with ESMTP id m59HpbL1046864 for ; Mon, 9 Jun 2008 17:51:37 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m59HpXqF2781226 for ; Mon, 9 Jun 2008 19:51:35 +0200 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m59HpWx6020644 for ; Mon, 9 Jun 2008 19:51:32 +0200 Received: from tuxmaker.boeblingen.de.ibm.com (tuxmaker.boeblingen.de.ibm.com [9.152.85.9]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with SMTP id m59HpSSv020533; Mon, 9 Jun 2008 19:51:29 +0200 Message-Id: <200806091751.m59HpSSv020533@d12av02.megacenter.de.ibm.com> Received: by tuxmaker.boeblingen.de.ibm.com (sSMTP sendmail emulation); Mon, 9 Jun 2008 19:51:28 +0200 Subject: Re: How can I get a memory map out of a core file? To: luisgpm@linux.vnet.ibm.com Date: Mon, 09 Jun 2008 17:52:00 -0000 From: "Ulrich Weigand" Cc: drow@false.org (Daniel Jacobowitz), bruce.korb@gmail.com (Bruce Korb), schwab@suse.de (Andreas Schwab), gdb@sourceware.org, eliz@gnu.org (Eli Zaretskii), msnyder@specifix.com (Michael Snyder) In-Reply-To: <1213028867.10042.101.camel@gargoyle> from "Luis Machado" at Jun 09, 2008 01:27:47 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/msg00057.txt.bz2 Luis Machado wrote: > Yes. Mainly giving the user the option to show exactly what we had > in /proc//maps right before the crash, so we know where things were > in memory, like the heap, stack and some specific shared libraries' > mappings. > > We currently can't do that. There's some information in the program > headers from a core file, like the one below, that show us a bit of > mapping-related information, but not enough so we can actually track > them down to a shared library. But shared library information should be available via "info sharedlibrary" (which uses the in-memory data structures allocated by ld.so, which are present in the core file) ... What is the extra information /proc//maps provides that you're concerned about? Bye, Ulrich -- Dr. Ulrich Weigand GNU Toolchain for Linux on System z and Cell BE Ulrich.Weigand@de.ibm.com