I have the same problem with you, but probably having a different cause. I'm using Debian 2.6.19.1. Supposedly, vDSO should no longer be mapped to a fixed address due to security reasons. The address should now be randomized:
$ cat /proc/self/maps 08048000-0804c000 r-xp 00000000 03:06 708671 /bin/cat 0804c000-0804d000 rw-p 00003000 03:06 708671 /bin/cat 0804d000-0806e000 rw-p 0804d000 00:00 0 [heap] b7b42000-b7c54000 r--p 003ca000 03:06 1570066 /usr/lib/locale/locale-archive b7c54000-b7e54000 r--p 00000000 03:06 1570066 /usr/lib/locale/locale-archive b7e54000-b7e55000 rw-p b7e54000 00:00 0 b7e55000-b7f7d000 r-xp 00000000 03:06 1703961 /lib/tls/libc-2.3.6.so b7f7d000-b7f82000 r--p 00127000 03:06 1703961 /lib/tls/libc-2.3.6.so b7f82000-b7f84000 rw-p 0012c000 03:06 1703961 /lib/tls/libc-2.3.6.so b7f84000-b7f87000 rw-p b7f84000 00:00 0 b7f9c000-b7f9d000 r--p 006cd000 03:06 1570066 /usr/lib/locale/locale-archive b7f9d000-b7f9f000 rw-p b7f9d000 00:00 0 b7f9f000-b7fa0000 r-xp b7f9f000 00:00 0 [vdso] b7fa0000-b7fb5000 r-xp 00000000 03:06 817622 /lib/ld-2.3.6.so b7fb5000-b7fb7000 rw-p 00014000 03:06 817622 /lib/ld-2.3.6.so bfe2d000-bfe43000 rw-p bfe2d000 00:00 0 [stack] However, the kernel still offers the option to use fixed mapping, which is the default, via CONFIG_COMPAT_VDSO. According to http://lwn.net/Articles/184734/ , when this is Y, it reverts to the old way - fixed address. Unfortunately, there's a bug in my version of kernel that defeats it (http://lkml.org/lkml/2007/1/14/2). I'm not sure whether there are still bugs in 2.6.22 or you have CONFIG_COMPAT_VDSO disabled. Could you paste the output of cat /proc/self/maps ? BTW, should GDB also be updated to support reading from a dynamically mapped vDSO? -- cannot read from linux-gate.so.1 https://bugs.launchpad.net/bugs/122314 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
