> Related to #74691?
according to this report, this is fixed with linux-2.6.22. closing.
** Changed in: gdb (Ubuntu)
Status: New => Fix Released
--
cannot read from linux-gate.so.1
https://bugs.launchpad.net/bugs/122314
You received this bug notification because you are a member of Ubun
setting CONFIG_COMPAT_VDSO to "n" and rebuilding my kernel (2.6.8-4)
made the problem go away for me.
--
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.
--
ub
Related to #74691?
--
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/mailma
I think this should tell you:
grep CONFIG_COMPAT_VDSO /boot/config-`uname -r`
I've the same error message with gdb under Feisty with a 2.6.22.1 kernel
built through make-kpkg, the grep on my system says:
$ grep CONFIG_COMPAT_VDSO /boot/config-`uname -r`
CONFIG_COMPAT_VDSO=y
--
cannot read from
As far as I know i don't have CONFIG_COMPAT_VDSO disabled, but I don't
know how to find that out.
here's my cat /proc/self/maps:
[EMAIL PROTECTED]:~$ sudo cat /proc/self/maps
08048000-0804c000 r-xp 08:01 14336006 /bin/cat
0804c000-0804d000 rw-p 3000 08:01 14336006 /bin/cat
0804d0
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 03:06 708671 /
GDB is trying to read from the vDSO either using ptrace or
/proc/PID/mem; I'm not sure which offhand.
--
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.
--
ub
