[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#319275: marked as done (libc6-dbg: unusable debug information files in /usr/lib/debug/lib)

Your message dated Sun, 22 Apr 2007 23:20:18 +0200
with message-id <20070422212016.GA9135@i386.aurel32.net>
and subject line Bug#319275: libc6-dbg: unusable debug information files in /usr/lib/debug/lib
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libc6-dbg
Version: 2.3.2.ds1-22
Severity: normal

Because files in /usr/lib/debug/lib lack all debug sections other than
.debug_frame, gdb fails to acquire debug information automatically
(See 15.2 Debugging Information in Separate of gdb.info).

IMHO, the package should have correct debug information files in all
possible (for each variant like tls) directories in the global debug
file directory.  Libraries with debug information in /usr/lib/debug
seem useless.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages libc6-dbg depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.5-1

On Wed, Jul 20, 2005 at 05:44:16PM -0400, Daniel Jacobowitz wrote:
> On Thu, Jul 21, 2005 at 06:04:37AM +0900, YAEGASHI Takeshi wrote:
> > Because files in /usr/lib/debug/lib lack all debug sections other than
> > .debug_frame, gdb fails to acquire debug information automatically
> > (See 15.2 Debugging Information in Separate of gdb.info).
> > 
> > IMHO, the package should have correct debug information files in all
> > possible (for each variant like tls) directories in the global debug
> > file directory.  Libraries with debug information in /usr/lib/debug
> > seem useless.
> 
> This is a feature.  The debug information for glibc is extremely large,
> and it makes GDB take an excessive amount of RAM to debug.  The files
> there have a functional .debug_frame and symbol table; this means that
> backtraces work, although they would not work without these files.
> 
> You can put /usr/lib/debug in LD_LIBRARY_PATH to get debug info, but we
> only ship one variant of these.  Again, because they are so large.
> 

Starting with glibc 2.5-1, we ship all variant of the library, because
there is only one variant. The linuxthreads version have been removed.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: