Package: gdb Version: 6.8.50.20090628-4 Severity: important I just wanted to do some C development and debuging of some problematic application on kFreeBSD and have problem with GDB.
bary...@debian:~$ gdb /bin/echo GNU gdb (GDB) 6.8.50.20090628-cvs-debian Copyright (C) 2009 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 "i486-kfreebsd-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... (no debugging symbols found) (gdb) run a Starting program: /bin/echo a Cannot access memory at address 0x5 (gdb) bt #0 0x280ef7b0 in ?? () (gdb) c Continuing. a Program exited normally. (gdb) q Debuging more complicated programs (like epiphany-browser) is impossible. (gdb) r Starting program: /usr/bin/epiphany-browser Cannot access memory at address 0x5 (gdb) c Continuing. Program received signal ?, Unknown signal. 0x298a10a7 in ?? () (gdb) c Continuing. warning: Signal ? does not exist on this system. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 7.2-1-686 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 gdb depends on: ii libc0.1 2.9-27 GNU C Library: Shared libraries ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libkvm0 7.2-3 FreeBSD kvm (kernel memory interfa ii libncurses5 5.7+20090803-2 shared libraries for terminal hand ii libreadline6 6.0-5 GNU readline and history libraries ii python2.5 2.5.4-2 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime gdb recommends no packages. Versions of packages gdb suggests: pn gdb-doc <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
