Debugging becomes a nightmare

We are using JDK 1.3.1_04 for our Swing desktop application
development on NT4SP6a.

When using one of the latest release versions of IDEA and stepping
throught the application, IDEA's debugger gets into a weird state (see
http://www.intellij.net/tracker/idea/viewSCR?publicId=9809) where
further stepping is not possible. You need to set a breakpoint and hit
the resume button (green triangle). This happens regulary one time in
two minutes. After a while the debugged application crashes (Dr.
Watson).

I do not think, that it's a JDK or NT problem, because debugging in
Eclipse 2.1 works very fine.

Because the latest EAP builds cannot be used for Swing application
development, I cannot try whether the problem is solved in EAP.
Therefore our only alternative is to use Eclipse (thanks god, that the
new version allows redefining the shortcuts, so it behaves nearly
IDEA-ish).

Does someone else has such debugging problems?

Tom

10 comments

On Thu, 03 Apr 2003 11:40:04 +0200, Thomas Singer wrote:

Because the latest EAP builds cannot be used for Swing application
development, I cannot try whether the problem is solved in EAP. Therefore


They can't? Tell that to my swing app!

0

At least with JDK 1.3, the JFrame does not show up.

Tom


"Mark Derricutt" <pinhead@satinism.org> schrieb:

>On Thu, 03 Apr 2003 11:40:04 +0200, Thomas Singer wrote:
>
>> Because the latest EAP builds cannot be used for Swing application
>> development, I cannot try whether the problem is solved in EAP. Therefore
>
>They can't? Tell that to my swing app!

0

The same is true with applets under JDK 1.3 as well. If you run the applet,
it never appears; comes up fine if you debug it though. There don't seem to
be any problems if you're using JDK 1.4.

There are two bug reports for this:
http://www.intellij.net/tracker/idea/viewSCR?publicId=10739 and
http://www.intellij.net/tracker/idea/viewSCR?publicId=10980

10980 is essentially a duplicate of 10739, but mentions applets instead of
Swing applications. 10739 is marked as fixed in build 810.

Clear? :)

Vil.

Thomas Singer wrote:

At least with JDK 1.3, the JFrame does not show up.

Tom


"Mark Derricutt" <pinhead@satinism.org> schrieb:

>>On Thu, 03 Apr 2003 11:40:04 +0200, Thomas Singer wrote:
>>
>>
>>>Because the latest EAP builds cannot be used for Swing application
>>>development, I cannot try whether the problem is solved in EAP. Therefore
>>
>>They can't? Tell that to my swing app!



--
Vilya Harvey, Consultant
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

0

I know, that it is fixed in 810. That's why I'm waiting for it
impatiently.

But nevertheless, I'm unsure, whether it solves the debugger problem.

Tom

0

Does turning on the "suspend all threads when stepping" option help?

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"



0

It is turned on.

Tom


"Eugene Zhuravlev" <jeka@intellij.com> schrieb:

>Does turning on the "suspend all threads when stepping" option help?

0

I report that same thing happened on my machine. In fact, another college's machine in the same environment has exectly same problem. It is very annoying and confused during debugging. In 3.0 there is not such problem. Only around 3.0.2 release.

OS: Window 2000 Server with SP2
IDEA: version 3.0.2(Build 696)
Project JDK:
java version "1.4.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)

When debugging and hit step over(F8) step by step, sometimes you just lost the highlight blue cursor. Then the resume button in debugging session enables. But you don't know which line the JVM is suspending at. To continue, I need to set another breakpoint several lines aftger and click the green triangle button to continue.
Because of this, I almost have to give up IDEA now.
Please fix this as soon as possible.

Now I installed 3.0.3, hope it is fixed.

0

>Now I installed 3.0.3, hope it is fixed.

I'm running 3.0.3 and it happens there, too.

Tom


java8964 <jiveadmin@jetbrains.com> schrieb:

>I report that same thing happened on my machine. In fact, another college's machine in the same environment has exectly same problem. It is very annoying and confused during debugging. In 3.0 there is not such problem. Only around 3.0.2 release.
>
>OS: Window 2000 Server with SP2
>IDEA: version 3.0.2(Build 696)
>Project JDK:
>java version "1.4.1_02"
>Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06)
>Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode)
>
>When debugging and hit step over(F8) step by step, sometimes you just lost the highlight blue cursor. Then the resume button in debugging session enables. But you don't know which line the JVM is suspending at. To continue, I need to set another breakpoint several lines aftger and click the green triangle button to continue.
>Because of this, I almost have to give up IDEA now.
>Please fix this as soon as possible.
>
>Now I installed 3.0.3, hope it is fixed.

0

This started happening on a bunch of machines at work when we got Windows XP. I've tried changing "suspend all threads", no direct draw and nothing helps. My target VM is 1.3.1_06 with "force classic VM" turned on. I'm going to try 3.0.4 and hope that fixes the problem.

Scott

0

Note to IntelliJ:

This issue is related to JAVA 1.3.1. After switching to JAVA 1.4.1, no
problems occur any more.

Tom

0

Please sign in to leave a comment.