Good tip. I was too pissed off for it to occur to me to check the log file. A little browsing through .log shows the culprit to be an ArrayIndexOutOfBoundsException in the tree for the stack view. I really can't be too bitchy about that, I suppose. I am using a milestone build, not a release build (but come on... the debug stack tree? That's not exactly a new feature). The shitty assed error dialog still pisses me off though.
5 comments:
You might get lucky and under the .metadata directory of your workspace there will be a .log file. It might have more details for you.
Good tip. I was too pissed off for it to occur to me to check the log file. A little browsing through .log shows the culprit to be an ArrayIndexOutOfBoundsException in the tree for the stack view. I really can't be too bitchy about that, I suppose. I am using a milestone build, not a release build (but come on... the debug stack tree? That's not exactly a new feature). The shitty assed error dialog still pisses me off though.
Oh, oh, can I be Eclipse?
In Taco's eyes, we are *all* Eclipse...
...until we prove otherwise.
Thanks for the title!
Stupid eclipse goes back in evolution!
Now I have to look for an old version to keep my old projects running.
Post a Comment