[Pydev-users] [pydev - Users] RE: Tracking down internal error

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3968571
By: mkearney

More detail...
The exact message is: "An internal error occurred during step over"

Symptoms of the problem have already appeared though. I believe, the first symptom
is that the window doesn't open to the point of the first breakpoint. This is
why I try stepping and ultimately encounter the step over error.

As an aside, I find that I often begin editing a source as soon as I see a problem
that can be fixed. Only later do I have the presence of mind to terminate the
running code. I probably shouldn't do that. However, I noticed several times
today that I was able to run debug, edit, terminate, rerun debug without a problem.
So at best that editing style is necessary but not sufficient to cause
the error.

Can pydev detect when a code is being changed and just terminate execution
automatically?

Other debuggers I have seen recently have a start
option in debugging. This sets a breakpoint on the  first line of execution,
starts the debugger. Consequently, it stops immediately. But I found that to
be useful data point.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649