Unhandled error
Wilts
Posts: 8
I having "fun" trying debug an intermittent problem with my camera controller project.· The project controls a Sony EVI-D30 camera giving a joystick interface etc.
Normally everything runs OK.· However after a while, the controller stops sending commands to the camera and resets.· Having connected up a PC and running it in debug mode I have concluded the following.
1)· There is no obvious memory leak - the heap and stack remain fixed and don't grow to infinity
2)· When the controller stops, the IDE reports the errors
· IDE-0042 - Unknown, unhandled exception in JVM 878
· IDE-0015 - Stack trace is corrupt
The Javelin stamp then resets.
I tried looking where the code had stopped using the debugger to try and work out where it had gone wrong - unfortunately it reports that it is in the exception class.· I then tried getting turning on my code test mode where it prints out lots of messages to the message windown.· Unfortunately it doesn't seem to go wrong.· I assume therefore that I might have a timing issue somewhere - the trouble is finding out where!
Are there any clues embedded in the IDE errror messages?· Is there anyway of working out what the JVM what was doing before the errror occured?
Thanks
Paul
·
Normally everything runs OK.· However after a while, the controller stops sending commands to the camera and resets.· Having connected up a PC and running it in debug mode I have concluded the following.
1)· There is no obvious memory leak - the heap and stack remain fixed and don't grow to infinity
2)· When the controller stops, the IDE reports the errors
· IDE-0042 - Unknown, unhandled exception in JVM 878
· IDE-0015 - Stack trace is corrupt
The Javelin stamp then resets.
I tried looking where the code had stopped using the debugger to try and work out where it had gone wrong - unfortunately it reports that it is in the exception class.· I then tried getting turning on my code test mode where it prints out lots of messages to the message windown.· Unfortunately it doesn't seem to go wrong.· I assume therefore that I might have a timing issue somewhere - the trouble is finding out where!
Are there any clues embedded in the IDE errror messages?· Is there anyway of working out what the JVM what was doing before the errror occured?
Thanks
Paul
·