From: Tom Horsley <tom.horsley@ccur.com>
To: linux-kernel@vger.kernel.org
Cc: bugsy@ccur.com
Subject: strange signal on new clone creation under ptrace?
Date: Thu, 08 Sep 2005 07:53:38 -0400 [thread overview]
Message-ID: <1126180418.11585.12.camel@tweety> (raw)
I'm seeing this on a redhat enterprise 4 system (so the kernel is
older than dirt in lkml time :-), but I wondered if it might
strike a familiar note to anyone working on ptrace issues.
In my debugger, I'm following clone and fork creation around
to debug children using PTRACE_SETOPTIONS. Normally when I get
the waitpid() status for a new clone, it shows up with SIGSTOP
as the initial reported signal. My debugger is expecting this
and handles it no problem.
In a hairy complex threads program a user has (which is apparently
using SIGUSR1 a lot), the very first status that ever shows up for
a brand new clone reports SIGUSR1 rather than SIGSTOP.
When I teach the debugger to deal with that and get the new clone
started up, it immediately gets the SIGSTOP I didn't get on the
initial status.
I haven't been able to create any test program to reproduce this
behavior, so I have no idea how it could happen, but it appears
as though the kernel managed to queue up the signals in the wrong
order.
Does this sound like a bug anyone remembers fixing? Does anyone
have an idea how I could make it happen? Just curious about what
the heck could be going on here (I can probably teach the debugger
to work around this as well).
reply other threads:[~2005-09-08 11:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1126180418.11585.12.camel@tweety \
--to=tom.horsley@ccur.com \
--cc=bugsy@ccur.com \
--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