From: "Gaël Deest" <GUtopiste@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11, 2.6.0-test9 and gdb 6.0
Date: Mon, 01 Dec 2003 00:53:51 +0100 [thread overview]
Message-ID: <3FCA830F.7080103@free.fr> (raw)
In-Reply-To: <20031130214025.GO2935@mail.muni.cz>
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...
prev parent reply other threads:[~2003-11-30 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 21:40 2.6.0-test11, 2.6.0-test9 and gdb 6.0 Lukas Hejtmanek
2003-11-30 23:53 ` Gaël Deest [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FCA830F.7080103@free.fr \
--to=gutopiste@free.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).