From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4139 invoked by alias); 4 Nov 2011 18:02:37 -0000 Received: (qmail 4131 invoked by uid 22791); 4 Nov 2011 18:02:36 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from co300216-co-outbound.net.avaya.com (HELO co300216-co-outbound.net.avaya.com) (198.152.13.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Nov 2011 18:02:23 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiUIAPQntE6HCzI1/2dsb2JhbABEqgN+B4F5EihRARUpQicEGxqda4QSm2SISGMEmWyMMg Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Nov 2011 14:02:22 -0400 Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 04 Nov 2011 13:51:25 -0400 Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.55]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 4 Nov 2011 14:02:22 -0400 From: "Worley, Dale R (Dale)" To: "gdb@sourceware.org" Date: Fri, 04 Nov 2011 18:02:00 -0000 Subject: Shared libaries and core files Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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/msg00026.txt.bz2 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? 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. Any information would be helpful, Dale