Jason Tackaberry <[EMAIL PROTECTED]> writes: > Anyway, I believe the problem is a race condition with the fork -- or > more specifically, the handler for SIG_CHLD. I'm doing gtk+ things > inside the handler, which of course can interrupt other gtk functions > and, I presume, cause some internal inconsistency.
Yeah, that would cause reentrancy. You can't do stuff in signal handlers. Well, only very very limited stuff. > So perhaps in lieu of that, I'll use a pipe(), add an input handler, and > just have the child write to the pipe when it's done. That way the > parent's flow is serialized. Yep, that's a good approach. Havoc _______________________________________________ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list
