From: Gokdeniz Karadag <gokdenizk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: incomplete si_codes for waitid(2) [patch available]
Date: Thu, 16 Apr 2009 19:11:20 +0300 [thread overview]
Message-ID: <49E758A8.1080406@gmail.com> (raw)
Hi,
In a program I was debugging, waitid(2) returned a strange value in siginfo_t
structure's si_code field. It was different that those stated in the man page
for waitid(2) [ waitid(2) man page is the same as wait(2) ].
When I looked at the relevant file "/usr/include/bits/siginfo.h" there were two
more values for si_code:
CLD_DUMPED, /* Child terminated abnormally. */
CLD_TRAPPED, /* Traced child has trapped. */
I was getting CLD_DUMPED value along with core dumps so I state that as an
example in the patch. I'm not sure about how a process can get CLD_TRAPPED but
I include it for completeness' sake.
The diff applies to today's git version.
============================== diff ======================
diff --git a/man2/wait.2 b/man2/wait.2
index c95ff2c..4028fae 100644
--- a/man2/wait.2
+++ b/man2/wait.2
@@ -310,6 +310,10 @@ Set to one of:
.BR _exit (2));
.B CLD_KILLED
(child killed by signal);
+.B CLD_DUMPED
+(child terminated abnormally, ie. core dump);
+.B CLD_TRAPPED
+(child has trapped while being traced);
.B CLD_STOPPED
(child stopped by signal); or
.B CLD_CONTINUED
==========================================================
--
Gokdeniz Karadag
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-04-16 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 16:11 Gokdeniz Karadag [this message]
[not found] ` <49E758A8.1080406-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-21 4:45 ` incomplete si_codes for waitid(2) [patch available] Michael Kerrisk
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=49E758A8.1080406@gmail.com \
--to=gokdenizk-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.