From: "H . J . Lu" <hjl@lucon.org>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] lin-lwp.c: Block SIGCHLD events when attaching
Date: Wed, 07 Nov 2001 15:15:00 -0000 [thread overview]
Message-ID: <20011119113832.A8778@lucon.org> (raw)
In-Reply-To: <1011119193045.ZM16376@ocotillo.lan>; from kevinb@cygnus.com on Mon, Nov 19, 2001 at 12:30:45PM -0700
On Mon, Nov 19, 2001 at 12:30:45PM -0700, Kevin Buettner wrote:
> When doing a lin_lwp_attach_lwp(), it is sometimes possible to receive
> a SIGCHLD signal thus causing the waitpid() call to fail with EINTR.
> This in turn causes the second assert() in lin_lwp_attach_lwp() to
> fail.
>
> Reproducing this problem can be somewhat difficult. I've only been
> able to reproduce it on a dual processor Linux/x86 machine. I did
> manage to reproduce it using the linux-dp program as follows:
>
Have you looked at
http://sources.redhat.com/ml/gdb/2001-09/msg00139.html
Specifically,
# gcc -g ex11.c -lpthread -lrt -D_GNU_SOURCE -static
# a.out
# gdb a.out
...
(gdb) att 14226
Attaching to program: /home/hjl/bugs/gdb/thread/a.out, process 14226
...
lin-lwp.c:620: gdb-internal-error: stop_wait_callback: Assertion `pid == GET_LWP (lp->ptid)' failed.
An internal GDB error was detected. This may make further
ex11.c is from glibc and 14226 is the first thread. Your patch may fix
it also.
H.J.
next prev parent reply other threads:[~2001-11-19 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 15:07 Kevin Buettner
2001-11-07 15:15 ` H . J . Lu [this message]
2001-11-07 19:05 ` Kevin Buettner
2001-11-07 19:37 ` Kevin Buettner
2001-11-07 20:26 ` H . J . Lu
2001-11-07 22:45 ` Kevin Buettner
2001-11-07 22:48 ` Kevin Buettner
2001-11-07 23:21 ` H . J . Lu
2001-11-08 10:55 ` Kevin Buettner
2001-11-08 10:25 ` H . J . Lu
2001-11-08 13:03 ` Mark Kettenis
2001-11-08 19:19 ` Kevin Buettner
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=20011119113832.A8778@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.com \
/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