Messages in this thread | | | Date | Wed, 15 Aug 2001 02:06:07 +1100 | From | (Bruce Janson) | Subject | Re: ptrace(), fork(), sleep(), exit(), SIGCHLD |
| |
In article <20010814092849.E13892@pc8.lineo.fr>, christophe =?iso-8859-1?Q?barb=E9?= <christophe.barbe@lineo.fr> wrote: .. >Le lun, 13 aoû 2001 10:29:32, Bruce Janson a écrit : .. >> The following program behaves incorrectly when traced: .. >Have you receive off-line answers? ..
No, though I did receive an offline reply from someone who appeared to have misunderstood the post. In case it wasn't clear, the problem is that the above program behaves differently when traced to how it behaves when not traced. (I do realise that in general, under newer Unices, when not ignored, a SIGCHLD signal may accompany the death of a child.)
>I guess that it's certainly more a strace issue and that it's perhaps ..
It's not clear to me whether it is a kernel, glibc or strace bug, but it does appear to be a bug. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |