Quote:
Originally Posted by Xenophon
I actually have built from source. That was reasonably straightforward, just by following the directions. I asked for advice on debugging (rather than building) quite intentionally.
My goal is to poke around in the debugger partly for my own amusement, and partly because doing so might lead to contributing some actual programming or debugging effort.
|
Fair enough. However I am not familiar with Eclipse - I use the JetBrains IdeaJ development environment. I use that on Windows, and I do not think that IdeaJ runs on a Mac (although I could be wrong). I would have thought that virtually any articles you can find on using Java with Eclipse on a Mac should be relevant.
You can also do work by simply using the IDE as a viewer/editor for making changes, rebuilding, running, and then examining the log files (assuming you have enabled trace level logging). I find that I often have to resort to that level of working to find problems that only get triggered a long way into a run so that interactive debugging is not really practical.
If you build from the latest source (now from Google Code rather than Launchpad) then you will notice a LOT of changes compared to the current release available for download. So much so that the next release is being promoted to be the first in the 3.0 series rather than the enxt in the 2.x series.