My application exists of multiple modules. If I set a breakpoint in the main module (the one with "if __name__ == '__main__':") the debugger stops correctly. But when choosing 'step into' the debugger continues executing the rest of the applications ignoring all breakpoints in the other modules. It doesn't step into the other modules either.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you give more info on your install? It's windows/linux? Are you using jython or python? Can you give some sample code that reproduces it? Do you have something in your error log?
Cheers,
Fabio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Problem occurs on both linux (ubuntu) and Windows Vista
It turns out that the debugger simply ignores all breakpoints that are not in the main executing module. Sample code is trivial: create 2 modules that use eachother, debug one module and put a breakpoint in the other.
Just curious: anybody here that succesfully debugged multiple modules? Which setup?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok... currently the jython debugger is having some problems... I still couldn't make it operate correctly in jython because of a number of bugs in the jython tracing facility (that the debugger uses). There's still no fix for it (and I don't even know if I'll be able to work around those bugs).
I've tried reproducing it on a 100% fail-safe way just using the jython tracing facility to report it to the jython guys, but until now I didn't have the time to do that properly... (and just saying: the tracing doesn't work for the pydev debugger even though it works for python doesn't seem like a proper report to me).
Cheers,
Fabio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PyDev: 1.3.9
Eclipse: 3.3 (Europa)
My application exists of multiple modules. If I set a breakpoint in the main module (the one with "if __name__ == '__main__':") the debugger stops correctly. But when choosing 'step into' the debugger continues executing the rest of the applications ignoring all breakpoints in the other modules. It doesn't step into the other modules either.
Can you give more info on your install? It's windows/linux? Are you using jython or python? Can you give some sample code that reproduces it? Do you have something in your error log?
Cheers,
Fabio
jython: 2.2
Problem occurs on both linux (ubuntu) and Windows Vista
It turns out that the debugger simply ignores all breakpoints that are not in the main executing module. Sample code is trivial: create 2 modules that use eachother, debug one module and put a breakpoint in the other.
Just curious: anybody here that succesfully debugged multiple modules? Which setup?
Ok... currently the jython debugger is having some problems... I still couldn't make it operate correctly in jython because of a number of bugs in the jython tracing facility (that the debugger uses). There's still no fix for it (and I don't even know if I'll be able to work around those bugs).
I've tried reproducing it on a 100% fail-safe way just using the jython tracing facility to report it to the jython guys, but until now I didn't have the time to do that properly... (and just saying: the tracing doesn't work for the pydev debugger even though it works for python doesn't seem like a proper report to me).
Cheers,
Fabio
Oh, and I wouldn't know where to find the error log. Googling for it says it should be here (which it isn't):
window->show view->other->PDE Runtime->Error log
There is no view 'PDE Runtime'
That's only if you have the sdk... if you don't, it should be in your workspace/.metadata/.log (just updated the faq to reflect that).
Cheers,
Fabio