public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4217] New: utrace: PTRACE_ATTACH of SIGSTOPped process hangs
Date: Tue, 20 Mar 2007 13:57:00 -0000 [thread overview]
Message-ID: <20070320135711.4217.cagney@redhat.com> (raw)
Opened by Jan Kratochvil (jan.kratochvil@redhat.com) on 2007-03-18 13:33
EST [reply] Private
Description of problem:
utrace implementation of ptrace(2) is incompatible:
PTRACE_ATTACH on a process being stopped (by SIGSTOP) never returns.
On non-utrace kernels it returns, tested:
kernel-2.6.20-1.2300.fc5.x86_64
linux-2.6.17.7.x86_64 (from kernel.org)
linux-2.6.16-xen.i686 (from kernel.org)
Version-Release number of selected component (if applicable):
kernel-xen-2.6.19-1.2898.2.3.fc7.i686
kernel-2.6.20-1.2925.fc6.i586
How reproducible:
Always.
Steps to Reproduce:
1. Process A should be: kill -STOP process_A_PID
2. Process B should: ptrace (PTRACE_ATTACH, process_A_PID, NULL, NULL);
3. Process B should: waitpid (process_A_PID, &status, 0);
Red Hat bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232837
--
Summary: utrace: PTRACE_ATTACH of SIGSTOPped process hangs
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: cagney at redhat dot com
OtherBugsDependingO 1496
nThis:
http://sourceware.org/bugzilla/show_bug.cgi?id=4217
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-03-20 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 13:57 cagney at redhat dot com [this message]
2007-10-04 20:24 ` [Bug general/4217] " jan dot kratochvil at redhat dot com
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=20070320135711.4217.cagney@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).