On Mon, Jan 4, 2010 at 12:32 PM, John David Anglin <dave@xxxxxxxxxxxxxxxxxx> wrote: >> e) Thus the child either crashes, overwrites memory of the parent or does other things wrong. > > I don't see how the forked child can affect the memory of the parent. > It can close files and affect the parent that way (child should use > _exit and not exit). > > If the forked child actually overwrites memory of the parent, this is > a big bug in the linux fork code. We have two bugs that are getting mixed here. Your original post has to do with a futex wait failure, this is possibly related to the hppa low level lock implementation. I am updating the hppa implementation to see if I can fix this for you. Helge's comments relate only to the vfork crash, and the Qt thread creation issue being seen by debian. Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
