Bug Squashing Tactics ...
posted 24 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Hello everyone,
I have made a GUI program that is called from native code. Basically the GUI runs as a screensaver. When the GUI is single-threaded (i.e. the GUI Thread only) the program runs flawlessly. However when I make it multi-threaded after a while the screensaver stops running and when I hit alt-ctrl-del I see that I have one or more Java tasks running in the background. So obviously something is wrong with my threading. I am having a heck of a time tracking the progress of the Java code since when the code is called from the native code, there is NO command prompt window and hence I can�t do the standard: System.out.println(�Executing X_Routine�), trick for debugging. I tried using a text file log, but if the program crashes before it closes the log, then I don�t get any debugging info. So I guess my two main questions are the following -
1) What is the best way to track down errors in such a situation.
2) I really, REALLY miss having output automatically directed to the command prompt window. Is there anyway that I can force this?
Thanks in advance
Dan
I have made a GUI program that is called from native code. Basically the GUI runs as a screensaver. When the GUI is single-threaded (i.e. the GUI Thread only) the program runs flawlessly. However when I make it multi-threaded after a while the screensaver stops running and when I hit alt-ctrl-del I see that I have one or more Java tasks running in the background. So obviously something is wrong with my threading. I am having a heck of a time tracking the progress of the Java code since when the code is called from the native code, there is NO command prompt window and hence I can�t do the standard: System.out.println(�Executing X_Routine�), trick for debugging. I tried using a text file log, but if the program crashes before it closes the log, then I don�t get any debugging info. So I guess my two main questions are the following -
1) What is the best way to track down errors in such a situation.
2) I really, REALLY miss having output automatically directed to the command prompt window. Is there anyway that I can force this?
Thanks in advance
Dan
posted 24 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
Log4J to the rescue, I'd think. Or, more low tech, flush() your debugging file after every write; a PrintStream or PrintWriter with autoFlush set to true should do.
- Peter
- Peter
Peter den Haan | peterdenhaan.com | quantum computing specialist, Objectivity Ltd
| Who knew that furniture could be so violent? Put this tiny ad out there to see what happens: Paul Wheaton's 16th Kickstarter: Gardening playing cards for gardeners and homesteaders https://coderanch.com/t/889615/Paul-Wheaton-Kickstarter-Gardening-playing |