1

Resolved

Breakpoints set before debugging is started are not hit

description

@route('/about')
@view('about')
def about():
    return dict(
        title = 'About',
        message = 'Your application description page.',
        year = datetime.now().year
    )
put a bkpoint on return & hit F5. the 1st time around it wont get hit. but if you delete & set the bkpoint again, it'll get hit. also, turning stdlib debugging on/off will affect it.

comments

Zooba wrote Jun 18 at 11:56 PM

If you have stdlib debugging off, breakpoints in the function directly called back from a stdlib function are not hit. If the breakpoint is one call deeper, it is hit correctly.

pminaev wrote Jun 19 at 2:01 AM

This is actually not about decorators, and not even about library code. Rather, we have a race condition on start debugging whereby the debugger tries to set breakpoints too early, before a connection is actually established. So this can be reproed even on a simple hello world type console app with enough luck.