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.
Using dev build 55 and tried to debug py project by setting a breakpoint but the debugger starts its debug shells but never reaches the debug point where it should become green.The debug session gets lost. I get the following error in the ide log due to this scenario: [Fatal Error] :1:101: The value of attribute "name" associated with an element type "CALL" must not contain the '<' character. org.netbeans.modules.python.debugger.backend.PythonDebugException: NBPython backend Parser parse SAX PARSING ERROR : The value of attribute "name" associated with an element type "CALL" must not contain the '<' character. ****************** XML-SOURCE ********************** <JPY> <CALL cmd="4" fn="d:\65cat\tutorial reviews\newpythonproject2\src\newpythonproject2.py" name="<module>" args="None" /></JPY> ****************** END OF XML-SOURCE ********************** at org.netbeans.modules.python.debugger.backend.JPyDebugXmlParser.parse(JPyDebugXmlParser.java:470) at org.netbeans.modules.python.debugger.backend.PythonDebugEvent.parse(PythonDebugEvent.java:111) at org.netbeans.modules.python.debugger.backend.PythonDebugEvent.<init>(PythonDebugEvent.java:161) at org.netbeans.modules.python.debugger.backend.PythonDebugClient.populateEvent(PythonDebugClient.java:168) at org.netbeans.modules.python.debugger.backend.PythonDebugClient.access$300(PythonDebugClient.java:21) at org.netbeans.modules.python.debugger.backend.PythonDebugClient$_TCP_TASK_.run(PythonDebugClient.java:142) LINE entered : d:\65cat\tutorial reviews\newpythonproject2\src\newpythonproject2.py:2 java.lang.IllegalArgumentException: Called DataObject.find on null at org.openide.loaders.DataObject.find(DataObject.java:477) at org.netbeans.modules.python.debugger.Utils.getLine(Utils.java:176) at org.netbeans.modules.python.debugger.PythonDebugger.handleDebuggerEvent(PythonDebugger.java:457) at org.netbeans.modules.python.debugger.actions.JpyDbgView.newDebuggingEvent(JpyDbgView.java:114) at org.netbeans.modules.python.debugger.gui.PythonDebugContainer$_DEBUGEVENT_MANAGER_.populateToPlugin(PythonDebugContaine r.java:661) at org.netbeans.modules.python.debugger.gui.PythonDebugContainer$_DEBUGEVENT_MANAGER_.populateLocalSource(PythonDebugConta iner.java:676) at org.netbeans.modules.python.debugger.gui.PythonDebugContainer$_DEBUGEVENT_MANAGER_.startupSourceInit(PythonDebugContain er.java:707) at org.netbeans.modules.python.debugger.gui.PythonDebugContainer$_DEBUGEVENT_MANAGER_.startDebugger(PythonDebugContainer.j ava:730) at org.netbeans.modules.python.debugger.gui.PythonDebugContainer$_DEBUGEVENT_MANAGER_.newDebugEvent(PythonDebugContainer.j ava:1039) at org.netbeans.modules.python.debugger.backend.PythonDebugClient.populateEvent(PythonDebugClient.java:169) at org.netbeans.modules.python.debugger.backend.PythonDebugClient.access$300(PythonDebugClient.java:21) at org.netbeans.modules.python.debugger.backend.PythonDebugClient$_TCP_TASK_.run(PythonDebugClient.java:142) entering animation
Created attachment 71725 [details] log file
the xml parsing problem should be fixed on last hudson builds. can you provide and attach a sample for the never reached debugger point problem ?
Created attachment 72108 [details] Sample project to debug
use build 55 to debug the sample project
The actual varsion of the debugger is single threaded => will only debug the main tread of a python program. The multi threading feature is in progress and should fix the problem you're faced with since the GUI action are handled under the control of AWT threads which are not monitored with current version I'll keep this ticket open until the multi threading feature is ready
cool... thanks jymen
the fix will be part of the multithreaded support extension which is in progress and planed for after the 65ea since the multithreading support is a big change in the debugger backend code , I do not want to take the risk of having regressions in the python65ea.
starting with build #513 this feature is now operation with jython 2.2.1 ... some problem still remaining with jython beta where some jython system libraries are in troubles when debugger traces are set ... I'll wait for jython 2.5 closer to release to check that again