Export to GitHub

spyderlib - issue #610

Feature Request: Improve debugging


Posted on Apr 4, 2011 by Happy Kangaroo

Spyder is very close to having a great built in debugger, but it needs a few more things.

I really want to be able to set up hot keys for stepping through code, ( stepping in, over, out, etc.)

It would also be nice if there was a "stack" tab for debugging that shows the current frame information.

Is there any plan for selecting threads while debugging?

Comment #1

Posted on Apr 4, 2011 by Happy Kangaroo

I've also noted that the GUI break point marks will become desynchronized from the real break points. For instance, if you have a break point on line 10, move to line 9 and hit enter the break point mark will move to line 11, but if you type b in pdb it reports the breakpoint is still at line 10 and it will still halt execution at line 10.

Comment #2

Posted on May 16, 2011 by Quick Horse

(No comment was entered for this change.)

Comment #3

Posted on Jul 27, 2011 by Happy Kangaroo

Just curious, but I have many tickets open related to debugging. Seeing these issues resolved is one of my most anticipated spyder enhancements. Any idea when these will be worked?

Comment #4

Posted on Jul 28, 2011 by Quick Horse

Hi Steve,

I've been thinking a lot about how to improve debugging in Spyder, specially because of your tickets and some others. They all show this area needs a lot of development to suit the people needs.

I haven't discussed this with Pierre, but in my opinion the best solution would be to develop a new plugin dedicated exclusively to debugging. It should have its dedicated console and variable explorer (to show the current stack), with some fancy buttons to move between breakpoints and keyboard shortcuts to do all the operations you describe.

We could also show plots generated while debugging with it. Right now this is impossible, because you can't start an event loop inside an ipython console that has started with an event loop (in some cases it works, but it makes Spyder prone to crashes).

Besides, editing frame variables with the variable explorer is not working now and I think it would be easier to solve with the plugin.

But as you can see, this means quite some work which has not even started. Pierre, what do you think about this? Is this the right path to follow or do you have other ideas?

Carlos

Comment #5

Posted on Feb 17, 2015 by Quick Horse

This issue was migrated to https://github.com/spyder-ide/spyder/issues/

The issue number is exactly the same

Status: New

Labels:
Type-Defect Priority-Medium Cat-Debugger Restrict-AddIssueComment-Commit