From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20564 invoked by alias); 4 Nov 2011 18:38:33 -0000 Received: (qmail 20556 invoked by uid 22791); 4 Nov 2011 18:38:33 -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; Fri, 04 Nov 2011 18:38:17 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RMOef-0007So-57 from pedro_alves@mentor.com ; Fri, 04 Nov 2011 11:38:17 -0700 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Nov 2011 18:38:14 +0000 From: Pedro Alves To: gdb@sourceware.org Subject: Re: Shared libaries and core files Date: Fri, 04 Nov 2011 18:38:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-12-generic; KDE/4.7.2; x86_64; ; ) Cc: "Worley, Dale R (Dale)" References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111041838.12151.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2011-11/txt/msg00028.txt.bz2 On Friday 04 November 2011 18:02:21, Worley, Dale R (Dale) wrote: > I see that when I give GDB a core file, GDB loads many shared > libraries into its memory model of the process being debugged. How > does GDB determine what these libraries are? Does GDB know of > libraries that are loaded "dynamically" in the course of execution, or > only those that are loaded at process start time? The former. > Naively, I would expect the dynamic loading routines in the process > would have to keep track of all the loaded libraries, and GDB could > extract from these data structures the complete list of libraries that > were loaded at the moment of the process failure. Correct. -- Pedro Alves