This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/22273] Improper assert in Linux posix_spawn implementation


https://sourceware.org/bugzilla/show_bug.cgi?id=22273

--- Comment #8 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Adhemerval Zanella from comment #7)
> (In reply to Andreas Schwab from comment #6)
> > You need to use a positive error number, not -1.
> 
> Indeed and still it won't help the case where the process is killed after
> setting args.err to 0 and I do not see how to correctly report it to user. 
> Even if we check waitpid unconditionally (with WNOHANG) for ec != 0 it might
> a case where the required program runs and it is killed just before the
> actual waitpid test. Any idea?

One option I have in mind is create the child with CLONE_CHILD_SETTID and call
set_tid_address with args.err as input (I am using set_tid_address to avoid
have to adjust each clone signature to take ctid in correct order).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]