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: | debugging project always step into UserDict.py source | ||
|---|---|---|---|
| Product: | python | Reporter: | Peter Lam <petersl> |
| Component: | Debugger | Assignee: | jymen <jymen> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | ||
| Priority: | P1 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | Windows Vista | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Peter Lam
2009-01-06 01:30:23 UTC
I followed the scenario but was not able to reproduce in Linux ubuntu : -> debugger does not enter UserDict.py and the breakpoint is hit correctly ; I made the test both with jython 2.2.1 and 2.5.b0+. I have been able to observe this problem before when some jython libs in current 2.5 beta are still buggy they may hit a debugger stop when they raise exceptions. So when I allways do a test with a python2.4 , Python 2.5 , jython 2.2.1 platform in that case. If those three platform PASSED then I wait for a more stable build of jython beta 2.5. I found any a bug when 'stop on first line' is unchecked and a breakpoint is set on first line that I fixed in #545. I also prevent jython systemlib UserDict.py to be controlled by debugger ... I think this should fix your problem since I suspect the UserDict.py to raise exception when under trace control. starting with 7.0 trunk build #545 and above I prevent UserDict.py to be traced by debugger. with build #550, it now steps into traceback.py at line 222. forgot to say that I used the bundled Jython 2.5b. With Python 2.4.4, debugging stepped into traceback.py line 219. With Python 2.5.2, it steps in traceback.py line 234. With Python 2.6, it also steps in line 234 and popped up the following exception as well. I'll install jython 2.2.1 to try if I can find one. Annotation: Was parsing C:\Python26\Lib\lib2to3\tests\data\py3_test_grammar.py Annotation: Was parsing C:\Python26\Lib\lib2to3\tests\data\py2_test_grammar.py Was parsing C:\Python26\Lib\lib2to3\tests\data\py3_test_grammar.py Was parsing C:\Python26\Lib\lib2to3\tests\data\py2_test_grammar.py Caused by: java.lang.ClassCastException Was parsing C:\Python26\Lib\lib2to3\tests\data\py3_test_grammar.py Was parsing C:\Python26\Lib\lib2to3\tests\data\py2_test_grammar.py Not reproducible for me with build 547 will try 550 next. Can't reproduce on Mac with build 551 for Jython nor Python platform projects. Maybe delete your user dir then try again? I have had some issues lately that were solved that way. Thanks for trying! I always started a new build from fresh userdir and created new projects to start with. Which version of python platform you use? I just installed jython 2.2.1 and got stepped in StringIO.py line 51. Perhaps there's a compatibility issue on Windows? I'll try linux to see if this problem exists. I verified in linux and this problem is not reproducible. looks like it's only happening on windows. I'm changing the OS to windows vista. Will try it on Windows XP. On Windows XP using the bundled jython 2.5b, it steps into traceback.py line 222. Ok guys , I think it's time for me to setup an XP virtual machine (snip...) and give it a try ;=) So I'll built that VM and will try to reproduce the issue then I am now able to reproduce that on an XP box ; I confirm that 's a WINDOWS specific regression on debugger's startup - The debuggee file name is not found (something truncated when filename contains spaces ??? I need to debug further). - then the python debugger enters an external exception and stop in the system traceback when creating a Python project the name of project and source is newpythonproject which on windows generate a filename like \newpythonproject => \n then was badly interpreted as control character when sending the filename over IP session which resulted in debugge file not found by the debugger session. fixed on trunk starting with hudson build #595 and above. verified in build 20090113-b599 |