I am having real trouble tracking down a bug and it would help be a lot to know which method called a certain method. Is there an easy way to get a call hierarchy from java? Java is a small part of the app so I cannot compile and run the whole app in eclipse/net beans so I don't have access to an IDE debugger's call hierarchy.
A:
Have you tried using Java's remote debugging capability? Google search to get you started if you haven't
Jim Barrows
2009-07-28 23:15:43
+10
A:
Thread.currentThread().getStackTrace();
or
Exception ex = new Exception();
ex.printStackTrace();
It's fairly slow, but fine for debugging purposes. API docs here.
Nelson
2009-07-28 23:15:47
A:
The best thing to do is throw an exception, immediately catch it and analyze the stack trace.
I believe that is how Log4J is capable of logging the calling method.
bogertron
2009-07-28 23:16:36
with Thread.dumpStack() or some such no need to throw an artificial exception.
djna
2009-07-28 23:17:56
You are correct that this is the way that log4j does it. I think thisi just for historical reasons though, since Java 1.5 the currentThread().getStackTrace() method suggested by Nelson is available so this approach is no longer necessary.
mikej
2009-07-28 23:19:50
A:
Java is a small part of the app so I cannot compile and run the whole app in eclipse/net beans so I don't have access to an IDE debugger's call hierarchy.
You dont need to run the app at all. If you make a project in Eclipse, you can use its built-in Call Hierarchy tool to find all of the possible places that call a method.
There is a trade off: The Call Hierarchy tool will give you ALL of the places from where a method is called. This is a good if you want/need to know all the possibilities. Neslson's suggestion of Thread.currentThread().getStackTrace() will give you the places from where a method is invoked during the process of you program for this invocation. The nuance is that you might not run through every code path during this invocation. If you are seeing specific behavior and want to know how you got there, use the getStackTrace() option.
akf
2009-07-28 23:48:23
A:
VS2010 presents anew future called Call Hierarchy of Methods that provides you with a tree view at design time
This tree view contains all (methods, prop., or whatever called the method) that calls the applied method
here is how try that in VS2010.
http://blog.flair-systems.com/2010/05/c-fastfood-call-hierarchy-of-methods.html
Waleed Mohamed
2010-05-28 15:51:59