Re: [Pydev-users] debugger ignores breakpoints
Brought to you by:
fabioz
From: peter <com...@ya...> - 2015-12-15 18:42:41
|
On 12/15/2015 04:44 PM, Fabio Zadrozny wrote: > > On Tue, Dec 15, 2015 at 10:34 AM, peter <com...@ya... > <mailto:com...@ya...>> wrote: > > hi, > > > im using eclipse 4.5.1 and pydev from http://pydev.org/updates. > breakpoints are just ignored and the program runs to the end, it works > for a method only containing a print statement...there pydev stops to > show debugging information. > > but for another method in the same file, it does not work. > that particular method as a for loop enclosing another, but the > debugger > just skipts straight to the end of that method and shows the output > after both loops ran to the end > > just above the first loop is a breakpoint. > > adding: > import pydevd > pydevd.settrace() > > source:http://stackoverflow.com/questions/9486871/pydev-breakpoints-not-working > > to the code says it cant find "pydevd" but the code stops a line below > settrace and i can run the for loops step by step. > > > any ideas? > > > Well, doing pydevd.settrace() adds a programatic breakpoint, so, it > should always work... as for why it doesn't work, on some situations > Python itself kills the debugging (for instance, if you have a > StackOverflowError anywhere, even if treated, it'll break the > debugger), and I know it can have some issues on some frameworks... > Can you give more details on your code? Do you have some code you can > share where I can reproduce the issue? > > Best Regards, > > Fabio set a breakpoint inside the method something, on my pc that thing prints 100 numbers and then quits instead of waiting for me class perfect_class(object): def __init__(self): pass def something(self): for i in range(10): for j in range(10): print i if __name__ == '__main__': x = perfect_class() x.something() |