From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Collect unexplained stopped threads in lin-lwp
Date: Wed, 18 Jun 2003 23:27:00 -0000 [thread overview]
Message-ID: <3EF0F576.8040305@redhat.com> (raw)
In-Reply-To: <20030618231609.GA394@nevyn.them.org>
Daniel Jacobowitz wrote:
> [Michael, you more or less approved this patch in December, but it's seen a
> few changes - linux_record_stopped_pid isn't a dummy any more.]
>
> This patch just accepts processes we aren't currently debugging which report
> a SIGSTOP, and throws them onto a list. Not very useful by itself, but my
> next patch will both cause this to happen (by enabling fork events) and
> empty the list when it receives fork events. I'm only submitting it
> separately, because it was the last meaningful piece I could break out.
>
> Is this OK?
>
I realize these are not the same as LWPs, but is there any reason
you can't throw them in the existing LWP list, and then pull them
out discriminately? (if that's a word...)
Just a suggestion. If there is a reason, then yes, approved.
next prev parent reply other threads:[~2003-06-18 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 23:16 Daniel Jacobowitz
2003-06-18 23:27 ` Michael Snyder [this message]
2003-06-18 23:33 ` Daniel Jacobowitz
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=3EF0F576.8040305@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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