Gremlins in Eclipse – shoot ‘em up
Twitter!
Last night, I lost a few hours and two kilogramms of nerves to solve the problems I didn’t even supposed to have. Something was wrong with the debugger and I couldn’t get the job done as debugger was highly uncooperative. Some of the issues were:
- Clicking on one line to toggle breakpoint, it appears in another
- Debugger skips the lines
- Changes in code sometimes doesnt’t effect the results in the firefox
- Feeling of a Gremlim infestation of your putter.
Some of you may laugh, but for the certain things, I didn’t have any knowledge of, and I didn’t find it anywhere, until my collegue Henrique Marino came to explain me how to end the suffering.
So, hereby I share it with you.
- If you have a CVS controlled code, with a branches, be sure that compiler is set to the particular branch that you work on at the moment. Go to (eclipse) Project -> Properties, select Flex Compiler and see what is written in “Additional compiler arguments”. Problem is probably there. This is the reason of debugger skipping the lines, if it is set wrongly.
- Close all projects except the one you use at the moment. Right click on a project and select “Close unrelated projects”
- If you use Jetty, since it’s not doing boring and time consuming deployment as JBoss, it creates another flaw: cache might not be cleaned. Go to Firefox, Tools -> Web developer -> Disable -> Disable cache.
This will kill the Gremlin(s).
I hope this post will shorten one’s suffering.

