Bug 197296 - Custom breakpoints are ignored
Custom breakpoints are ignored
Status: CLOSED WONTFIX
Product: python
Classification: Unclassified
Component: Debugger
6.x
Macintosh Mac OS X
: P3 (vote)
: TBD
Assigned To: jymen
issues@python
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-31 20:00 UTC by kenorb
Modified: 2017-06-23 08:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments
jpy debug file (155.04 KB, application/x-gzip)
2011-03-31 20:00 UTC, kenorb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kenorb 2011-03-31 20:00:55 UTC
Created attachment 107413 [details]
jpy debug file

Debugger works till main code is executed.
That means some of the files can't be debugged by breakpoints.
Probably there is one piece of code which tricks debugger.
Maybe this?
    sys.exit(main(sys.argv[1:]))

Basically what happen, I'm going step by step, and in some step, it showing me green line (like debugger stopped on breakpoint), but the output produces script output (as it's run) and when it's finish, I've following error:
>>>System Exit REQUESTED BY DEBUGGEE  =0['Traceback (most recent call last):
', '  File "/Users/kenorb/projects/ants/aichallenge/ants/playgame.py", line 156, in <module>
    sys.exit(main(sys.argv[1:]))
', 'SystemExit: 0

See attachment for details.
Comment 1 kenorb 2011-03-31 20:04:10 UTC
Basically it's this line:
        result = run_game(game, bots, engine_options, round)
when I go inside (F7) it,  execution automatically continue the execution ignoring the debugger.

Definition of that function:
def run_game(game, botcmds, options, gameid=0):

File is loaded in different way that usually:
sys.path.append("../worker")
from engine import run_game

Maybe that's why?
Comment 2 kenorb 2011-04-06 19:58:51 UTC
Maybe it's because my script uses subprocess module and the breakpoint is inside Sandbox?
Comment 3 Jenselme 2017-06-22 22:13:23 UTC
Should be solved with the new debugger when we add it. The debugger is currently disabled. Closing this since there is no point into importing it elsewhere.
Comment 4 Jiri Kovalsky 2017-06-23 08:06:05 UTC
Thanks for your evaluation Julien. Reporter, if you think your issue is still valid and needs to be addressed, don't hesitate to reopen it with additional information. Closing for now.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo