Spyder: Feature Request: Improve debugging

[spyder-bot]

_From [email protected] on 2011-04-04T11:54:24Z_

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?

_Original issue: http://code.google.com/p/spyderlib/issues/detail?id=610_

[spyder-bot]

_From [email protected] on 2011-04-04T10:37:58Z_

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.

[spyder-bot]

_From ccordoba12 on 2011-05-15T19:31:43Z_

Labels: Cat-Debugger

[spyder-bot]

_From [email protected] on 2011-07-27T11:30:36Z_

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?

[spyder-bot]

_From ccordoba12 on 2011-07-28T08:29:09Z_

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

[CAM-Gerlach]

The main requests I see here:

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

Implemented, at least as of 3.2.x

I've also noted that the GUI break point marks will become desynchronized from the real break points.

This is apparently fixed by at least 3.2.6; just tested now and everything worked properly.

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

This part is a duplicate of the more focused #1613

Therefore, it would seem this issue should be closed.