M
Marc Rochkind
I'm executing a raw UNIX fork system call in JNI code. In 1.3.x, that and
what came next worked perfectly, near as I can tell.
But, upon switching to 1.4.2, I notice that an exception thrown in the
child hangs the process... this worked fine in 1.3.x.
I can think of various explanations. (Example: a fork() preserves only a
single thread, and other threads that might have been in the parent are, in
the child, terminated. Perhaps the exception stuff was multi-threaded.)
But, does anyone know of something done specifically that broke this in
1.4.x?
--Marc
what came next worked perfectly, near as I can tell.
But, upon switching to 1.4.2, I notice that an exception thrown in the
child hangs the process... this worked fine in 1.3.x.
I can think of various explanations. (Example: a fork() preserves only a
single thread, and other threads that might have been in the parent are, in
the child, terminated. Perhaps the exception stuff was multi-threaded.)
But, does anyone know of something done specifically that broke this in
1.4.x?
--Marc