From: Andreas Schwab <schwab@suse.de>
To: storm@cua.dk (Kim F. Storm)
Cc: Sam Steingold <sds@gnu.org>, emacs-devel@gnu.org
Subject: Re: busyloop in sigchld_handler
Date: Fri, 16 Mar 2007 10:59:04 +0100 [thread overview]
Message-ID: <jemz2dmrvb.fsf@sykes.suse.de> (raw)
In-Reply-To: <m3fy85lefj.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Fri, 16 Mar 2007 10:34:40 +0100")
storm@cua.dk (Kim F. Storm) writes:
> The man pages talks about "stopped processes" -- it doesn't mention
> (un)traced processes at all.
There are two classes of stopped processes: traced ones and untraced
ones. See the rationale section in the POSIX manpage. ptrace is not part
of the standard, so it is generally ignored in the normative part of it.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-03-16 9:59 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 18:33 busyloop in sigchld_handler Sam Steingold
2007-03-11 19:39 ` Kim F. Storm
2007-03-11 19:43 ` David Kastrup
2007-03-11 19:51 ` Sam Steingold
2007-03-11 20:42 ` Kim F. Storm
2007-03-11 21:06 ` Sam Steingold
2007-03-11 21:14 ` Eli Zaretskii
2007-03-11 21:17 ` Sam Steingold
2007-03-11 21:51 ` Eli Zaretskii
2007-03-11 22:21 ` Sam Steingold
2007-03-12 4:24 ` Richard Stallman
2007-03-12 7:00 ` David Kastrup
2007-03-13 2:43 ` Richard Stallman
2007-03-11 22:27 ` Andreas Schwab
2007-03-11 22:30 ` Kim F. Storm
2007-03-12 17:37 ` Andreas Schwab
2007-03-12 17:53 ` Sam Steingold
2007-03-12 18:45 ` Andreas Schwab
2007-03-12 18:57 ` Sam Steingold
2007-03-12 19:28 ` Andreas Schwab
2007-03-12 19:34 ` David Kastrup
2007-03-12 21:36 ` Andreas Schwab
2007-03-13 7:29 ` David Kastrup
2007-03-13 9:29 ` Andreas Schwab
2007-03-13 22:19 ` David Kastrup
2007-03-13 22:28 ` Andreas Schwab
2007-03-13 22:54 ` David Kastrup
2007-03-13 23:17 ` Andreas Schwab
2007-03-14 7:06 ` David Kastrup
2007-03-14 9:24 ` Kim F. Storm
2007-03-14 10:00 ` David Kastrup
2007-03-14 10:22 ` Andreas Schwab
2007-03-14 10:52 ` David Kastrup
2007-03-14 11:01 ` Andreas Schwab
2007-03-14 11:12 ` David Kastrup
2007-03-14 12:29 ` Andreas Schwab
2007-03-14 10:01 ` Andreas Schwab
2007-03-14 13:15 ` Kim F. Storm
2007-03-14 13:41 ` Andreas Schwab
2007-03-14 14:10 ` Kim F. Storm
2007-03-14 14:12 ` Andreas Schwab
2007-03-14 15:02 ` Kim F. Storm
2007-03-14 16:34 ` Andreas Schwab
2007-03-16 9:34 ` Kim F. Storm
2007-03-16 9:59 ` Andreas Schwab [this message]
2007-03-14 3:24 ` Richard Stallman
2007-03-14 17:34 ` David Kastrup
2007-03-26 1:47 ` YAMAMOTO Mitsuharu
2007-03-26 2:02 ` Sam Steingold
2007-03-26 2:17 ` YAMAMOTO Mitsuharu
2007-03-28 10:02 ` Kim F. Storm
2007-03-28 15:19 ` Chong Yidong
2007-03-28 15:25 ` Andreas Schwab
2007-03-28 15:33 ` Kim F. Storm
2007-03-28 15:37 ` Andreas Schwab
2007-03-28 20:18 ` Kim F. Storm
2007-03-29 17:59 ` Richard Stallman
2007-03-28 15:30 ` Alfred M. Szmidt
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jemz2dmrvb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=sds@gnu.org \
--cc=storm@cua.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).