Netbeans debugger doesn't work

I’m using Netbeans as the IDE for developing my Panda3D game in Python. Normal development works fine, but when I try to launch the debugger, it only works up to the run() method call. The debugger then dies and the debugging session ends.

Has anyone experienced the same problem? Any ideas on how to fix it? I really wish I could debug my application properly! :frowning:

[LOG]PythonDebugger : overall Starting
[LOG]PythonDebugger.taskStarted : I am Starting a new Debugging Session ...
[LOG]This window is an interactive debugging context aware Python Shell 
[LOG]where you can enter python console commands while debugging 
>>>[stdout:]DirectStart: Starting the game.
args =  ['C:\\Users\\Joao\\.netbeans\\6.9\\config\\nbPython\\debug\\nbpythondebug\\', 'localhost', '29100']
localDebuggee= None
Known pipe types:
(all display modules loaded.)
JPyDbg connecting  localhost  on in=  29100 /out= 29101
JPyDbgI0001 : connected to  localhost
>>>Exception in thread MainThread:
Traceback (most recent call last):
  File "C:\Programs\Panda3D-1.7.0\python\lib\", line 525, in __bootstrap_inner
  File "C:\Users\Joao\.netbeans\6.9\config\nbPython\debug\nbpythondebug\", line 593, in run
    exec self._cmd in self._myglobals,self._mylocals
  File "<string>", line 1, in <module>
  File "D:/Joao/Academic/UFRJ/Projeto Final/Panda/src/", line 40, in <module>
  File "C:\Programs\Panda3D-1.7.0\direct\showbase\", line 2531, in run
  File "C:\Programs\Panda3D-1.7.0\direct\task\", line 496, in run
  File "C:\Programs\Panda3D-1.7.0\direct\task\", line 450, in step
    signal.signal(signal.SIGINT, self.keyboardInterruptHandler)
ValueError: signal only works in main thread

Debug session normal end

Just for the record, I’m using Netbeans 6.9, Panda 1.7.0 and Windows 7 64-bits.

Debugging on IDLE works, but it’s awfully slow to the point of being unusable.

PS: I’m not sure if Scripting Issues is the best forum for posting this. In case it’s not, I’m sorry!

It appears that Panda doesn’t want to run if it’s not on the main thread. Apparently your debugger is executing your code (and by extension Panda) in a background thread, so it can poke and prod it. Not sure if there’s anything that can be done about that, but I’m trying to find out. I’ve posted the question here:

[Running Panda not on the main thread: possible?)