printstacktrace

I am going through a socket program. In it, printStackTrace is called on the IOException object in the catch block. What does printStackTrace() actually do? catch(IOException ioe) { ioe.printStackTrace(); } I am unaware of its purpose. What is it used for? Joachim Sauer It's a method on Exception instances that prints the stack trace of the instance to System.err . It's a very simple, but very useful tool for diagnosing an exceptions. It tells you what happened and where in the code this happened. Here's an example of how it might be used in practice: try { // ... } catch (SomeException e) { e

In my code snippet below, the printStackTrace() method is called in the catch block . After running the program you can see that sometimes the printStackTrace() runs several times in a row instead of running in the order of printStackTrace() --> catch block --> finally block . If you change the static boolean b to false then the System.out.print(e) executes in order. So why does the printStackTrace() behaves in different way? (something with the threads??) public class PrintStackTrace { static boolean b = true; public static void main(String[] args){ for(int i = 0; i < 100; i++){ try{ throw

In my application, I am running my code through PMD.It shows me this message: Avoid printStackTrace(); use a logger call instead. What does that mean? It means you should use logging framework like logback or log4j and instead of printing exceptions directly: e.printStackTrace(); you should log them using this frameworks' API: log.error("Ops!", e); Logging frameworks give you a lot of flexibility, e.g. you can choose whether you want to log to console or file - or maybe skip some messages if you find them no longer relevant in some environment. If you call printStackTrace() on an exception the

Is it a bad idea to use printStackTrace() in Android Exceptions like this? } catch (Exception e) { e.printStackTrace(); } Julian Yes, it is a bad idea. You should instead use Android's built-in log class specifically designed for these purposes: http://developer.android.com/reference/android/util/Log.html It gives you options to log debug messages, warnings, errors etc. Logging errors with: Log.e(TAG, "message", e) where the message can be an explanation of what was being attempted when the exception was thrown or simply Log.e(TAG, e) if you do not wish to provide any message for context You

I have a regular C# code. I have no exceptions . I want to programmatically log the current stack trace for debugging purpose. Example: public void executeMethod() { logStackTrace(); method(); } Spence Have a look at the System.Diagnostics namespace. Lots of goodies in there! System.Diagnostics.StackTrace t = new System.Diagnostics.StackTrace(); This is really good to have a poke around in to learn whats going on under the hood. I'd recommend that you have a look into logging solutions (Such as NLog, log4net or the Microsoft patterns and practices Enterprise Library) which may achieve your