This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Python debugger does not honour break points in multiple files | ||
|---|---|---|---|
| Product: | python | Reporter: | anthony_flury <anthony_flury> |
| Component: | Debugger | Assignee: | jymen <jymen> |
| Status: | CLOSED WONTFIX | ||
| Severity: | blocker | CC: | Jenselme |
| Priority: | P2 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
If additional log files etc will help please don't hesitate to ask for them. Same here. Windows XP, Netbeans 6.7.1, jython 2.5.0 I cannot step into a function in a different file. The breakpoint behavior is funny: if the breakpoint is in a different file, it does not stop there. But sometimes it highlights it afterward: e.g. when the execution reaches the end but the program is still running because I've opened a Java Swing window. Ubuntu 9.04, Netbeans 6.7.1, Python 2.6.2: same behaviour Windows XP, Netbeans 6.8 M1, Python 2.6.2: same behaviour NOTE: if "stop at first line" is unchecked in tools > preferences, you can stop at breakpoint in module b, but any further action (F7 or F8) are disabled. Just F5 works. Same behavior. Product Version: NetBeans IDE 6.7 (Build 200906251104) Java: 1.5.0_19; Java HotSpot(TM) Client VM 1.5.0_19-137 System: Mac OS X version 10.5.8 running on i386; MacRoman; en_US (nb) Bug is still open in 6.9,one year later. same thing happens in ruby on 6.9.1 Still waiting for an answer on this one - fails in 6.9 also (as mentioned above). 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. 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. |
The python debugger in 6.7 is unable to debug across multiple files. Although it will execute all the functionality correctly, it wont step into any other module, or honour break points in any other modules. Repro : 1) Create a new python project - based on either the netbeans python platform or the linux python 2.5.2 platform. 2) write a trivial program using module a as the main program which imports and calls a function defined in module b 3) place a break point in modules a and b 4) run the debugger on the application, and step through line by line What you expect to happen : The debugger would stop at the break point defined in module b, or be able to step into the function in module b. What actually happens The debugger executes the function in module b, but ignores the break point in module b and is unable to step into module b. Module a : ---------------------------------- import b def testa(): print "test a 1" print "test a 2" if __name__ = "main" : testa() b.testb() ----------------------------------- module b : ----------------------------------- def testb(): print "test b 1" print "test b 2" -----------------------------------