This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/22273] Improper assert in Linux posix_spawn implementation
- From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 12 Oct 2017 09:00:45 +0000
- Subject: [Bug libc/22273] Improper assert in Linux posix_spawn implementation
- Auto-submitted: auto-generated
- References: <bug-22273-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22273
--- Comment #10 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Andreas Schwab from comment #9)
> Killing the child between args.err = 0 and exec is not a problem, that can
> be considered a successful spawn, and the caller will eventually call wait
> and note the signal (if he is interested in it). In fact, I think any
> signal that happens between fork and exec should be relayed to the caller to
> figure out, as if spawn was successful.
This seems reasonable, in this case I think we should set ec equal 0 for
WIFSIGNALED in my suggestion at comment #5.
--
You are receiving this mail because:
You are on the CC list for the bug.