To analyse the flow of program logic, step by step is called tracing. Usually you would use a tool called a debugger to do this for you. One simple tool is Throwable.getStackTrace() which will tell you where you are in the code, and how you got there. The following technique lets you put the name of the current method in error messages, or the name of the caller of the currrent method, or its caller etc. You might use it something like this:
imAt() in the following code sample will print out at com.mindprod.mypackage.Myclass.doSomething line 34. You could use similar code to return the name of the current class or method. Unfortunately, support for the methods this relies on is not guaranteed in all implementations.
In older Javas you will have to make do with new Throwable().printStackTrace(), or you can catch an exception and print with e.printStackTrace(). Thread.dumpstack() is a convenience method to do just that.
available on the web at:
optional Replicator mirror
Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Your face IP:[22.214.171.124]
|Feedback||You are visitor number 26,441.|