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

Re: How to use -dbg packages (and specifically libncurses5-dbg) ?



Le 15/09/2010 13:55, Timo Juhani Lindfors a écrit :
> (gdb) shell pidof nano
> 23506
> (gdb) attach 23506
> Attaching to process 23506
> Reading symbols from /bin/nano...(no debugging symbols found)...done.
> Reading symbols from /lib/libncursesw.so.5...Reading symbols from /usr/lib/debug/lib/libncursesw.so.5.7...done.
> (no debugging symbols found)...done.
> Loaded symbols for /lib/libncursesw.so.5
> Reading symbols from /lib/libc.so.6...Reading symbols from /usr/lib/debug/lib/libc-2.11.2.so...done.
> (no debugging symbols found)...done.
> Loaded symbols for /lib/libc.so.6
> Reading symbols from /lib/libdl.so.2...Reading symbols from /usr/lib/debug/lib/libdl-2.11.2.so...done.
> (no debugging symbols found)...done.
> Loaded symbols for /lib/libdl.so.2
> Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.11.2.so...done.
> (no debugging symbols found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> 0x00007f0d65f47ea0 in __read_nocancel () at ../sysdeps/unix/syscall-template.S:82
> 82      ../sysdeps/unix/syscall-template.S: No such file or directory.
>         in ../sysdeps/unix/syscall-template.S
> Current language:  auto
> The current source language is "auto; currently asm".
>   

 Here is what I get with similar commands :

> gdb
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
(gdb) shell pidof nano
22973
(gdb) attach 22973
Attaching to process 22973
Reading symbols from /bin/nano...(no debugging symbols found)...done.
Reading symbols from /lib/libncursesw.so.5...(no debugging symbols
found)...done.
Loaded symbols for /lib/libncursesw.so.5
Reading symbols from /lib/libc.so.6...Reading symbols from
/usr/lib/debug/lib/libc-2.7.so...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libdl.so.2...Reading symbols from
/usr/lib/debug/lib/libdl-2.7.so...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/ld-linux-x86-64.so.2...Reading symbols from
/usr/lib/debug/lib/ld-2.7.so...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2

(no debugging symbols found)
0x00007fe6fa4819e0 in __read_nocancel () from /lib/libc.so.6
(gdb)

And I checked that I really have the -dbg packages :

> env COLUMNS=120 dpkg -l |grep curses
ii  lib32ncurses5            5.7+20081213-1           shared libraries
for terminal handling (32-bit)
ii  libncurses5              5.7+20081213-1           shared libraries
for terminal handling
ii  libncurses5-dbg          5.7+20081213-1          
debugging/profiling libraries for ncurses
ii  libncurses5-dev          5.7+20081213-1           developer's
libraries and docs for ncurses
ii  libncursesw5             5.7+20081213-1           shared libraries
for terminal handling (wide character support)
ii  libncursesw5-dbg         5.7+20081213-1          
debugging/profiling libraries for ncurses
ii  libncursesw5-dev         5.7+20081213-1           developer's
libraries for ncursesw
ii  mtr                      0.73-1                   Full screen
ncurses and X11 traceroute tool
ii  ncurses-base             5.7+20081213-1           basic terminal
type definitions
ii  ncurses-bin              5.7+20081213-1           terminal-related
programs and man pages
ii  ncurses-term             5.7+20081213-1           additional
terminal type definitions
ii  pinentry-curses          0.7.5-2.1                curses-based PIN
or pass-phrase entry dialog for GnuPG


I tested this on a Debian Lenny system, with amd64 architecture.


   Thanks for your help,
        Fred.


Reply to: