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 libraries and separate debugging files

From: "Worley, Dale R (Dale)" <dworley at avaya dot com>
To: Baurzhan Ismagulov <ibr at radix50 dot net>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Thu, 25 Aug 2011 15:20:32 -0400
Subject: RE: Shared libraries and separate debugging files
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5852@DC-US1MBEX4.global.avaya.com>,<20110824222150.GM25065@radix50.net>

> From: Baurzhan Ismagulov [ibr@radix50.net]
> 
> Debian has it working OOTB. E.g., /lib/libc-2.11.2.so has its
> corresponding /usr/lib/debug/lib/libc-2.11.2.so. FWIW, one can build a
> hello, world and step into printf.

In the situation I am working within, the library files of the
execution host have been copied into a working directory of a
different host for analysis of the core file.  So /lib/libc-2.11.2.so
has been copied into /home/foo/crash1/lib/libc-2.11.2.so, and its
debug file is in /home/foo/crash1/usr/lib/debug/lib/libc-2.11.2.so.
But there does not appear to be a way to configure GDP to understand
the connection between the two files.

Dale

Follow-Ups:
- Re: Shared libraries and separate debugging files
  - From: Jan Kratochvil

References:
- Shared libraries and separate debugging files
  - From: Worley, Dale R (Dale)
- Re: Shared libraries and separate debugging files
  - From: Baurzhan Ismagulov

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