Displaying 2 results from an estimated 2 matches for "wifcontinu".
Did you mean:
wifcontinued
2014 Oct 03
0
Fwd: mksh-static segfaults on continued jobs
...rashing immediately after that.
The crash happens in j_print() at jobs.c:1560 where the expression
sigtraps[WSTOPSIG(p->status)] is out-of-bounds. It seems to be introduced
with revision 1.101 of jobs.c that added WCONTINUED flag to wait(2)
and then updated the state after checking status with WIFCONTINUED.
Apparently, when compiling with klibc, WCONTINUED flag is defined but
WIFCONTINUED macro is not. The result is that p->state and p->status
are not consistent.
This fixes it for me:
--- jobs.c 10 Jun 2014 22:17:33 -0000 1.104
+++ jobs.c 3 Oct 2014 04:33:32 -0000
@@ -1339,7 +1339,7 @@...
2002 May 12
1
"Unexplained error code xxx" in rsync-2.5.5
...t_process(). A call to WEXITSTATUS(*status)
must only happen, when WIFEXITED(*status) returns true.
Else, WIFSIGNALED(*status) could be true, in which case the process was
terminated by a signal. One has to extract the signal number using
WTERMSIG(*stat)... and so on. There is also WIFSTOPPED() and
WIFCONTINUED().
(mk)
--
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
>> Im pr?motorischen Cortex kann jeder ein Held sein. (bdw) <<