This project has moved and is read-only. For the latest updates, please go here.


Support mixed mode C/Python debugging


This would be great feature which would enable users to step from Python code into C++ code and vice-versa.

file attachments

Closed Jul 1, 2013 at 6:52 PM by RickWinter
Mixed mode debugging is now available in 2.0 Beta. Pick it up, give it a whirl, and let us know what you think


FFakie wrote Mar 12, 2012 at 8:23 AM

I'm desperately waiting this one, and if you are too, at the moment you can try using WinDbg to debug C++ part while using VS2010 to debug Python part instead of re-attaching to native/Python. You can't use any other instance of Visual Studio (2008, 2010) to debug C++ part. Maybe it could work with older Visual Studio though.

andrewdelong wrote Aug 16, 2012 at 8:29 PM

This is also the #1 feature that would make my life easier.

einaren wrote Dec 14, 2012 at 12:46 PM

This feature is likely to make Python Tools the preferred python editor for Windows devs in my company.

sandeepnshelke wrote Jan 8, 2013 at 7:12 AM

In our company we are developing the software using Python and C++ and need to put in debug messages while debugging which cumbersome and time consuming process. This tool will make the debugging more simple.

mwesterdahl76 wrote Feb 5, 2013 at 9:23 AM

Yes, I can't even begin to describe how valuable this is.
As einaren say, this will really be setting a new standard for everyone when this starts to work.

I think it already has a high votecount, so hopefully you'll start on this soon?

At least, it would be nice to hear an ETA from you, so that we'll now.

Zooba wrote Feb 5, 2013 at 4:40 PM

We're actively looking into this right now, but we're acutely aware of unexpected complications. With a bit of luck, we'll have something in our next release later this year, but it may only have limited functionality.

If you're really keen to get hold of this, leave a comment here and make sure that we can contact you directly. We'll probably be able to get some early previews out if you're willing to test and send in diagnostic information (for example, code and minidumps).

einaren wrote Feb 6, 2013 at 9:44 AM

@Zooba This is great news! I'll gladly help test this.

(I miss this feature every day)

mwesterdahl76 wrote Feb 6, 2013 at 12:16 PM

@zooba: I too would like to participate in the testing. Thx!

mwesterdahl76 wrote Mar 19, 2013 at 10:10 AM

Hi, I noticed that this feature wasn't in the 2.0 alpha release. Would you mind giving us a status update?

Zooba wrote Mar 19, 2013 at 4:45 PM

Working hard on it right now. Give us a month or two to get the core features into place and we'll have more to share.

stevenmbiz wrote Mar 22, 2013 at 2:05 AM

@zooba: Sounds great! I definitely like to participate in the testing.

cuongtong wrote Mar 31, 2013 at 2:12 PM

I'd like to help testing this feature as well please !

pminaev wrote May 17, 2013 at 9:42 PM

We're actively working on this feature with the aim to ship a usable (if not entirely on par feature-wise with regular Python debugging - certain things are much more complicated in the mixed world) implementation in the upcoming PTVS release. Stay tuned!

stevenmbiz wrote May 20, 2013 at 5:19 AM

Simply awesome!

Zooba wrote Jun 3, 2013 at 7:55 PM

Just a little teaser:


I don't know about you guys, but I'm at least as excited about this as you all are. Great work, pminaev!

einaren wrote Jun 27, 2013 at 9:30 AM

This may be a game changer. Unfortunately for me, I'm bound to VS2010. Makes me cry, but great work pminaev!