This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Shared libaries and core files

From: Pedro Alves <pedro at codesourcery dot com>
To: gdb at sourceware dot org
Cc: "Worley, Dale R (Dale)" <dworley at avaya dot com>
Date: Fri, 4 Nov 2011 18:38:11 +0000
Subject: Re: Shared libaries and core files
References: <CD5674C3CD99574EBA7432465FC13C1B225CA60137@DC-US1MBEX4.global.avaya.com>

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

Follow-Ups:
- RE: Shared libaries and core files
  - From: Worley, Dale R (Dale)

References:
- Shared libaries and core files
  - From: Worley, Dale R (Dale)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]