My problem is that JDebug will appear to hang during debugging, with
the message:
"No response to command (process = <x>, timeout=10)"
I posted about this last week to see if anyone else had seen the
problem. I can only reproduce the problem when I am using the junit
test harness. Someone did respond to me that they have no problem
using junit with jde. So, I've tried to break down my code to get it
to hang on a small test case without junit. Unfortunately, I've been
unable to reproduce the problem when I remove junit from my code, so
I'm resorting to post a test case along with the junit.jar file.
If anyone has a few minutes to try this and verify whether or not it
hangs on their system, it would help me a lot. I'm attaching the code
(test.tgz) and the junit jar file (junit.jar), along with my jde
problem report environment. To run it, untar the the code and add the
directory containing it to your jde source directory and classpath,
and also add junit.jar to your classpath. Set a breakpoint at line
127 of Database.java ("seek(recNum)") and at line 48 of
TestRunnerIT2.java (first line of main()). Then start jdebug, and
each time line 127 of Database.java is hit, do jde-bug-continue
(continue under the jdebug menu item).
What happens to me is that for the few seeks it will work, but then I
get the "no response to command" problem (by the 7th or so seek).
I'm running jde2.2.0 on a RedHat 6.1 system with xemacs 21.1 and the
sun 1.2.2 (minor version 006) jdk. I have removed the jde that came
bundled with xemacs, so it isn't that I'm accidentally using the wrong
version of jde.
Thanks in advance for any help with this,
Laurie Tynor
[EMAIL PROTECTED]
jdeProblemCode.tgz
junit.jar
jdeProblemReportEnvironment.txt
