public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4330] New: utrace: PTRACE_CONT SIGSTOP should not kill
Date: Fri, 06 Apr 2007 17:52:00 -0000 [thread overview]
Message-ID: <20070406185246.4330.jan.kratochvil@redhat.com> (raw)
Opened by Jan Kratochvil (jan.kratochvil@redhat.com) on 2007-04-06 13:46
EST [reply] Private
Description of problem:
Found a regression against kernel.org in RH kernels utrace based implementation
of ptrace(2).
Version-Release number of selected component (if applicable):
kernel-2.6.20-1.3045.fc7.x86_64
(on FC6 system)
How reproducible:
Always.
Steps to Reproduce:
1. gcc -o stopkills stopkills.c -Wall -ggdb3
2. ./stopkills
Actual results:
./stopkills: PTRACE_DETACH: No such process
Expected results:
(nothing; exit code 0)
Additional info:
ptrace (PTRACE_CONT, child_pid, NULL, (void *) SIGSTOP);
ptrace (PTRACE_DETACH, child_pid, NULL, NULL);
PTRACE_DETACH fails by ESRCH on the utrace kernels.
Red Hat bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235521
--
Summary: utrace: PTRACE_CONT SIGSTOP should not kill
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: jan dot kratochvil at redhat dot com
OtherBugsDependingO 1496
nThis:
http://sourceware.org/bugzilla/show_bug.cgi?id=4330
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-04-06 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 17:52 jan dot kratochvil at redhat dot com [this message]
2007-09-19 20:20 ` [Bug general/4330] utrace: ptrace operations should work on child in job control stop 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=20070406185246.4330.jan.kratochvil@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).