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

Bug#401482: vdso patch doesn't work against 2.6.18.dfsg.1-13etch1



I built a kernel from linux-source-2.6.22 version 2.6.22-4 with
the .config taken from linux-image-2.6.22-2-k7 version 2.6.22-4.

        $ uname -r
        2.6.22-fixdso
        
        $ gdb sleep
        (no debugging symbols found)
        Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
        (gdb) run 300
        Starting program: /bin/sleep 300
        (no debugging symbols found)
        (no debugging symbols found)
        (no debugging symbols found)
        (no debugging symbols found)
        (no debugging symbols found)
        
        Program received signal SIGINT, Interrupt.
        0xffffe410 in __kernel_vsyscall ()
        (gdb) bt full
        #0  0xffffe410 in __kernel_vsyscall ()
        No symbol table info available.
        #1  0xb7ee2e10 in __nanosleep_nocancel () from /lib/i686/cmov/libc.so.6
        No symbol table info available.
        #2  0x0804a194 in ?? ()
        No symbol table info available.
        #3  0xbfe6ece8 in ?? ()
        No symbol table info available.
        #4  0x00000000 in ?? ()
        No symbol table info available.

It's a shame to hear that this doesn't work for stable's kernel,
although I'm happy to hear that *someone* has tested the patch... I've
given up waiting for a response from the Debian kernel team. A shame,
since gdb has been useless on i386 for over a year, and will presumably
continue to be useless on etch until the end of time. :(

PS: please CC me in messages to this report, otherwise I won't receive
your messages... :)

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078

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


Reply to: