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

Bug#595161: marked as done (libc6-dbg: zero documentation)

Your message dated Wed, 01 Sep 2010 17:51:02 +0200
with message-id <4C7E7666.1090106@aurel32.net>
and subject line Re: Bug#595161: libc6-dbg: zero documentation
has caused the Debian Bug report #595161,
regarding libc6-dbg: zero documentation
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
595161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595161
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-dbg
Version: 2.11.2-2
Severity: important

Hi,

I'd like to point out that there is zero documentation telling you what libc6-dbg
is supposed to be useful for. The only thing that it installs in /usr/share/doc
are the changelogs that are bytewise identical to those in libc6 and libc6-dev.

Are we supposed to link to these libraries when building debuggable
applications?  Can they be replaced at runtime with some LD_ magic? My simple
attempts at setting LD_LIBRARY_PATH to /usr/lib/debug/lib are ignored (since
there no libc.so.6 symlinks), and LD_PRELOADing
/usr/lib/debug/lib/libc-2.11.2.so just makes my applications segfault.

Any help appreciated.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33-rc5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6-dbg depends on:
ii  libc6                         2.11.2-2   Embedded GNU C Library: Shared lib

libc6-dbg recommends no packages.

libc6-dbg suggests no packages.

-- no debconf information
-- 
[*Thomas  Themel*] The game of life is to keep the SF's score low. If you do
[extended contact] something bad in life, the SF gets two points. If you
[info provided in] don't do something good you should have done, the SF gets
[*message header*] one point. You never score, so the SF always wins. - Erdős

--- End Message ---
--- Begin Message --- 
Thomas Themel a écrit :
> Package: libc6-dbg
> Version: 2.11.2-2
> Severity: important
> 
> Hi,
> 
> I'd like to point out that there is zero documentation telling you what l=
> ibc6-dbg
> is supposed to be useful for. The only thing that it installs in /usr/sha=
> re/doc
> are the changelogs that are bytewise identical to those in libc6 and libc=
> 6-dev.
> 
> Are we supposed to link to these libraries when building debuggable
> applications?  Can they be replaced at runtime with some LD_ magic? My si=
> mple
> attempts at setting LD_LIBRARY_PATH to /usr/lib/debug/lib are ignored (si=
> nce
> there no libc.so.6 symlinks), and LD_PRELOADing
> /usr/lib/debug/lib/libc-2.11.2.so just makes my applications segfault.
> 
> Any help appreciated.
> 

There is nothing to do, gdb use them by default, like the zillions of
-dbg packages that are already in the archive.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: