Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.apps,comp.os.linux.development.system Subject: Re: Status = 2943 from waitpid? Date: Thu, 09 Jun 2011 13:51:15 +0100 Lines: 14 Message-ID: <8739jjnp6k.fsf@sapphire.mobileactivedefense.com> References: <033817d4-c109-4d37-a476-f7710b7ed829@a10g2000vbz.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net KIWueoYdmi3G6KHa2+rbIw15Z+ot4fc5pxkSDXeoY9tQq35/U= Cancel-Lock: sha1:ygBy60O2DbyK1+joo5ILxM1eFK4= sha1:cvUs0Zuq2mzpE8JLtGH3Nfyez/M= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.development.apps:141 comp.os.linux.development.system:161 Jeffrey Walton writes: > I'm ptrace'ing a process. After fork/exec and then a wait on the > child, I'm getting a status of 2943. I'm testing for failure, but > waitpid reports non-failure. I've looked in , but the > value 2943 is not defined and does not appear to be a bit mask. > > Any ideas on where I should look? At the corresponding hexnumber which is 0xb7f, meaning (AFAIK), your process was stopped by a SIGSEGV. A fairly human-readable version of the code generating and analysing these numbers should be in /usr/include/bits/waitstatus.h. The relevant macro is #define __W_STOPCODE(sig) ((sig) << 8 | 0x7f)