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: "Worley, Dale R (Dale)" <dworley at avaya dot com>
To: Pedro Alves <pedro at codesourcery dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Fri, 4 Nov 2011 16:54:21 -0400
Subject: RE: Shared libaries and core files
References: <CD5674C3CD99574EBA7432465FC13C1B225CA60137@DC-US1MBEX4.global.avaya.com> <201111041838.12151.pedro@codesourcery.com> <CD5674C3CD99574EBA7432465FC13C1B225CA6013C@DC-US1MBEX4.global.avaya.com>,<201111042040.08118.pedro@codesourcery.com>

i> From: Pedro Alves [pedro@codesourcery.com]
> 
> $ gdb /path/to/program -c /path/to/core
> (gdb) info sharedlibrary
> 
> Or were you thinking of something else?

I wasn't aware of "info sharedlibrary".

What I want is something that can be done from the command line.  It
looks like

gdb [executable] -c [core] -silent -ex 'info sharedlibrary' -ex quit

will suffice.  The output from that can be postprocessed to make a
list of the libraries.

Thanks!

Dale

References:
- Shared libaries and core files
  - From: Worley, Dale R (Dale)
- Re: Shared libaries and core files
  - From: Pedro Alves
- RE: Shared libaries and core files
  - From: Worley, Dale R (Dale)
- Re: Shared libaries and core files
  - From: Pedro Alves

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