Re: libc6-dbg

[Colin Watson <cjwatson@debian.org>]

On Thu, Aug 08, 2002 at 03:34:25PM -0400, Sven Heinicke wrote:
> With stable, when I do a `apt-cache show libc6' I get two different
> versions:
> 
> Version: 2.2.5-10
> Version: 2.2.5-6
> 
> But when I do a 'apt-cache show libc6-dbg` only get one version:
> 
> Version: 2.2.5-6

libc6-dbg 2.2.5-10 is certainly available among woody's security
updates.

> I ask because I am trying to debug some inhouse software that works fine
> or Red Hat and Mandrake but Segmentation faults on Debion.  In gdb it
> gives me little help where the problem in:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 3076 (LWP 6149)]
> 0xc13fe195 in ?? ()
> (gdb) where
> #0  0xc13fe195 in ?? ()
> Cannot access memory at address 0x1
> (gdb)
> 
> even though th running program in compiled with debugger info.  So I was
> going to try to link with the debugging clib and see if it tells me where
> I am.

libc6-dbg probably won't help you there anyway, since your program's
stack is corrupt: 0x1 is not the address of any real piece of code. Once
that happens, you can't really believe the backtrace. You'll need to
catch it before it segfaults to find out what's going on.

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]