DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27614>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27614 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2006-10-12 13:32 ------- I've got the same thing happening to me, but I'm using the <java> task instead of <junit>. If I fork="true" the child and run it in the background (in GNU/Linux) then it blocks on a signal, and if I don't fork it it's fine. If, after it blocks, I bring it to the foreground, it will then proceed. I worked around the problem by adding an input="/dev/null" attribute to the java element, so it looks as if some code in junit depends on having stdin (even though it doesn't appear to read from it). Does anyone know how to get a thread dump of the child process? If I redirect the child's stdout and stderr to files and "kill -3" the child I don't get the thread dump in either the out or err files. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
