Paul Clapham wrote:I believe Zahro means that Eclipse is acting as if there were a breakpoint at that line.
Seems to me the first thing to do would be to look at how your breakpoints are configured. Not only can you configure specific lines to be breakpoints, you can configure them to be conditional breakpoints also. I'm guessing that neither of those two apply in this case. However I believe you can also configure Eclipse to break when exceptions are thrown -- maybe that's only specific exceptions, I don't recall and I haven't opened up Eclipse to poke through its configuration options. So maybe that was done in the past, and the guilty line of code you posted is throwing an exception in that category. Having a line of code in the standard API which throws an exception wouldn't be an abnormal thing, remember. Other standard API code would very likely catch it and deal with it as a normal happening.
If you press the "carry on" button in the debug options, do things continue in the normal way?
Thank you! You are right, it turns out an exception was being raised at that line, and my Debug options in Eclipse were set to "Suspend execution on uncaught exceptions". I unchecked this and it no longer breaks there. Slightly annoying because I would like the option of having that in my own code, but I suppose I can live without it if it means not having to resume a breakpoint every time I start the app :)