CODEWITHSUNDEEP
javaswingruntime-error
AndroidDev
AndroidDev

Reputation: 21237

Strategies for debugging a runtime Java crash that runs correctly in NetBeans

Sorry in advance. This is a really vague question because I have no idea whatsoever what is going on. I have a Java Swing GUI desktop app that I wrote in NetBeans. While inside of NetBeans, the app works fine and passes all of the tests that I have thrown at it. I've been developing this app over the past several months, deploying it at various phases of its development.

Yesterday, I finished adding and testing some new functionality. I built the application and put it on another computer. I then went to run the program (outside of NetBeans) straight from the jar file. While in the new areas (JDialog boxes), the program crashes. Since I am not in an IDE, I have no feedback to see what is wrong.

The only thing that I can think of (and this is lame) is that I added some switch statements that switch on strings, which I know to new to 1.7. I was previously developing in 1.6. Otherwise, I can think of no reason that the program should work flawlessly inside the IDE, but crash outside of it.

Can anyone offer any suggestions for how I should approach this? I'm at a complete loss.

Thanks very much.

Upvotes: 2

Views: 350

Answers (2)

Boris Gavrilman
Boris Gavrilman

Reputation: 31

I would start from collecting a crash dump data. If you run the UI on windows you could use DrWatson

If you run the UI in Linux , By default the heap dump is created in a file called java_pidpid.hprof in the working directory of the VM. unless you specify the path yourself by adding this -XX:HeapDumpPath= option to your UI java options.

Upvotes: 1

djechlin
djechlin

Reputation: 60788

The next debugging step for you is reducing the size of your program until it doesn't crash, then seeing what change you made worked. That should either make the answer obvious or give you a good question to post on SO.

Your idea that it might have to do with switch statements tells you to try:

  • removing them
  • removing and compiling on JDK 6 and see if it works

Those are reasonable ways to reduce your program size to see if you can make it run.

Upvotes: 1

Related Questions