From: Kevin Buettner <kevinb@cygnus.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] lin-lwp.c: Block SIGCHLD events when attaching
Date: Wed, 07 Nov 2001 22:48:00 -0000 [thread overview]
Message-ID: <1011120071710.ZM17562@ocotillo.lan> (raw)
In-Reply-To: Kevin Buettner <kevinb@cygnus.com> "Re: [PATCH RFA] lin-lwp.c: Block SIGCHLD events when attaching" (Nov 19, 11:53pm)
On Nov 19, 11:53pm, Kevin Buettner wrote:
> I just tried it. It seems to behave about the same. It usually attaches
> okay, but I am able to reproduce the "Cannot find new threads: generic error"
> by using Jim's trick of repeatedly attaching and detaching.
I now know a little bit more about this problem.
First, I should explain that I'm using Jim Blandy's trick of
set height 0
break <somewhere that will be hit by one or more threads>
while 1
attach <pid of main process>
continue
detach
end
The "Cannot find new threads: generic error" seems to occur just (or
shortly) after one of the early threads has exited. Tomorrow, I'll
write a test to see if it's possible at all to attach to a
multithreaded process in which one of the threads has exited.
Kevin
next prev parent reply other threads:[~2001-11-20 7:17 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
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 [this message]
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=1011120071710.ZM17562@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hjl@lucon.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