Wednesday, March 5, 2008  Debugging and Profiling - same, not
different  Why is it that Eclipse has such a great debugger, but
such a extremely poor profiler?  I've used JProfiler and YourKit
Profiler, and find both products interesting (however, JProfiler
gets my money). However, they are a just that slight tad too
awkward to fire up - I don't use them often enough, so it is not
"in the fingers" in the same way I always run my programs
through the Eclipse debugger.  The Eclipse profiler, when I've
gotten it to work, which is a real PITA, is amazingly slow -
I've never been able to profile even the simplest applications.
I wonder if it doesn't use some XML format to transfer the
profiling information from the profiled application to the
profiler..  The Eclipse debugger, on the other hand, is a truly
wonderful tool - for what it is made for.  Then, one suddenly
starts to wonder: aren't these two things pretty much the same
stuff? Both the debugger and the profiler needs to be able to
inspect the objects on hea