Jan 21, 2013 at 10:31 AM
Edited Jan 21, 2013 at 4:38 PM
Sorry if this is explained somewhere, but I just couldn't find any special info that would allow me to do this, so I'm basically assuming that the feature is not working so well?
I'm trying to attach to a very simple python program, via MSVS 2012 using the "Python Debugging" as code type.
I locate the process via the "os.getpid()" which was suggested in one of the threads, but when MSVS attaches, the "symbols" won't really load proparly (I guess).
If I look at the modules window, it's empty. This is very different from when the debugger is launched via F5.
Also, the suggested "Break All" method won't work. It says "Unable to break execution. This process is not currently executing the type of code that you selected to debug"
The breakpoints are "valid" in the sense that they are red (as opposed to hollow with a warning on them)
The program itself looks like this:
print "PID", os.getpid()
for i in range(100):
print "i", i
And it's invoked by c:\python27_64\python.exe test.py
If I debug the program via the F5 key, the breakpoints work fine.
Any advice on how to get this working?
It just occurred to me to test the 32-bit version. And lo and behold, it worked fine!
So it's apparently a 64-bit issue.
It seems to behave similarly to this issue https://pytools.codeplex.com/workitem/926