Dear Debian folks,

Am Mittwoch, den 05.12.2012, 13:19 +0100 schrieb Paul Menzel:
> Package: libjavascriptcoregtk-1.0-0-dbg
> Version: 1.8.1-3.3
> Severity: important

[…]

> despite having `libjavascriptcoregtk-1.0-0-dbg` installed, attaching
> with GDB to a WebKit based browser like Midori or a core dump file, it
> complains that it does not find the debugging symbols.
> 
>         […]
>         Reading symbols from /usr/lib/libwebkitgtk-1.0.so.0...Reading symbols 
> from /usr/lib/debug/usr/lib/libwebkitgtk-1.0.so.0.13.2...(no debugging 
> symbols found)...done.
>         (no debugging symbols found)...done.
>         Loaded symbols for /usr/lib/libwebkitgtk-1.0.so.0
>         Reading symbols from /usr/lib/libjavascriptcoregtk-1.0.so.0...Reading 
> symbols from /usr/lib/debug/usr/lib/libjavascriptcoregtk-1.0.so.0.13.2...(no 
> debugging symbols found)...done.
>         (no debugging symbols found)...done.
>         Loaded symbols for /usr/lib/libjavascriptcoregtk-1.0.so.0
>         […]
> 
> Furthermore the generated backtraces are incomplete like in bug 684583 [1].
> 
>         Thread 6 (Thread 0xb2cf1b70 (LWP 6255)):
>         #0  0xb76cb424 in __kernel_vsyscall ()
>         No symbol table info available.
>         #1  0xb4e26de6 in nanosleep () at 
> ../sysdeps/unix/syscall-template.S:82
>         No locals.
>         #2  0xb4e26c10 in __sleep (seconds=0) at 
> ../sysdeps/unix/sysv/linux/sleep.c:138
>                 ts = {tv_sec = 0, tv_nsec = 73466461}
>                 set = {__val = {65536, 0 <repeats 31 times>}}
>                 oset = {__val = {0, 0, 2999914756, 3038455568, 3038789543, 
> 3077479012, 0, 0, 5, 0, 1, 3066726480, 1, 3077476340, 2999914880, 
>                     3066726920, 2999914836, 3038412912, 3066726480, 0, 
> 4294967295, 3077476340, 3038789543, 5, 2999914736, 3077413910, 0, 3, 
>                     720896, 3034941487, 3042221908, 2829455104}}
>                 result = <optimized out>
>         #3  0xb547d0e4 in WTF::TCMalloc_PageHeap::scavengerThread() () from 
> /usr/lib/libjavascriptcoregtk-1.0.so.0
>         No symbol table info available.
>         #4  0xb547d16b in WTF::TCMalloc_PageHeap::runScavengerThread(void*) 
> () from /usr/lib/libjavascriptcoregtk-1.0.so.0
>         No symbol table info available.
>         #5  0xb4eeec39 in start_thread (arg=0xb2cf1b70) at 
> pthread_create.c:304

in #debian on <irc.oftc.net> the user jm_ helped me to find out more
information. But unfortunately still no solution could be found.

                $ file 
{,/usr/lib/debug}/usr/lib/libjavascriptcoregtk-1.0.so.0.13.2
                /usr/lib/libjavascriptcoregtk-1.0.so.0.13.2:               ELF 
32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, 
BuildID[sha1]=0x87f1ecd596e60352fd7dc672f13e72a5f30d7545, stripped
                /usr/lib/debug/usr/lib/libjavascriptcoregtk-1.0.so.0.13.2: ELF 
32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, 
BuildID[sha1]=0x87f1ecd596e60352fd7dc672f13e72a5f30d7545, not stripped

So it is no incompatibility. On the other hand, it is no path issue
either as GDB finds the debugging symbols from for example Rhythmbox,
which also puts the files directly under `/usr/lib/debug/`.

        $ dpkg -L rhythmbox-dbg
        […]
        /usr/lib/debug/usr/lib/rhythmbox
        […]
        /usr/lib/debug/usr/lib/librhythmbox-core.so.6.0.0
        […]
        $ gdb -q rhythmbox
        Reading symbols from /usr/bin/rhythmbox...Reading symbols
        from /usr/lib/debug/usr/bin/rhythmbox...done.
        done.
        (gdb)


Thanks,

Paul


> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684583
[2] http://packages.debian.org/search?keywords=rhythmbox-dbg

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to