Hello,
is there any issue about using gdb with pthreads under 2.6.0-test9+ kernels?
With 2.6.0-test11 I got message while du next over a function that creates some
threads:
Program received signal SIG32, Real-time event 32.
__pthread_sigsuspend (set=0xbffff6d0)
???at ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c:5656
../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c: No such file or directory.
in ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c
(gdb)
With 2.6.0-test9 I got a message about gdb cannot read thread registers.
With 2.4.x series it is ok. Is it a bug in ptrace in kernel or a bug in gdb?
--
Luk?? Hejtm?nek
Lukas Hejtmanek wrote:
>Hello,
>
>is there any issue about using gdb with pthreads under 2.6.0-test9+ kernels?
>
>With 2.6.0-test11 I got message while du next over a function that creates some
>threads:
>
>Program received signal SIG32, Real-time event 32.
>__pthread_sigsuspend (set=0xbffff6d0)
> at ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c:5656
> ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c: No such file or directory.
> in ../linuxthreads/sysdeps/unix/sysv/linux/pt-sigsuspend.c
>(gdb)
>
>With 2.6.0-test9 I got a message about gdb cannot read thread registers.
>
>With 2.4.x series it is ok. Is it a bug in ptrace in kernel or a bug in gdb?
>
>
>
I've got exactly the same problem...