|
From: Xavier B. <xav...@fr...> - 2004-10-01 16:15:10
|
Hi, I have a program which I can debug fine with gdb (I can trace throught it, I can list functions and peek variables, etc.) but when attaching gdb to it through valgrind (--db-attach=yes) I can see no symbols: (gdb) bt #0 0x52bff042 in ?? () #1 0x009e60f3 in ?? () #2 0x1d143298 in ?? () #3 0x1d13d5e3 in ?? () #4 0x00000004 in ?? () #5 0x1d4b5130 in ?? () #6 0x00000090 in ?? () #7 0x1d06813c in ?? () #8 0x52bfd818 in ?? () #9 0x1d064150 in ?? () #10 0x00000004 in ?? () #11 0x1d4b5130 in ?? () #12 0x00000090 in ?? () #13 0x1cf13d2c in ?? () #14 0x00000000 in ?? () Is this a known bug ? Is there a workaround ? I'm under Fedora Core 2 (up-to-date), I tried a self-build valgrind rpm (from the 2.2.0 srpm) and the rpm from ftp://fr2.rpmfind.net/linux/fedora/core/development/i386/Fedora/RPMS/valgrind-2.2.0-1.i386.rpm both don't work. Thanks, Xav |