This is still not fixed in 2.18.5. Breakpoint only works first time. After continuing, the code runs at full speed but the breakpoint won't trigger again. Clearing breakpoint in the admin screen and re-adding it makes no difference. Clearing removes the breakpoint from the admin screen but puts an error on the console "*** DO_CLEAR failed Non-numeric breakpoint number (all})"
On Saturday, October 6, 2018 at 3:07:30 PM UTC-4, Massimo Di Pierro wrote: > > We will address this in 2.17.3 > > On Friday, 5 October 2018 13:52:17 UTC-7, David Manns wrote: >> >> I occasionally use the admin debugger package to investigate problems >> when running in my test environment on Windows 10 using the source >> distribution of web2py and Python 2.7 >> >> When I place a breakpoint on the code and execute my test case the >> interactive debugger is triggered, and I can step through code, examine >> variables, etc. When I have gathered the information I need and click >> 'continue' the application indeed continues and can be used as normal >> (though I think it runs slowly, as if the debugger is still checking). >> >> The problem is that the debugger will no longer work. Code will execute >> straight through either previously or newly set breakpoints without going >> into debug mode. Only shutting down the test server and restarting it works. >> >> I raised this a long time ago in the context of 2.16.1, problem still >> exists in 2.17.1. >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
