No "Python/Native Debugging" option when debugging a native (embedding) application crash dump

Hi,

After installing the Python native tools I am able to attach the mixed-mode debugger to my application, which embeds Python, and that works great.

However, I sometimes have to debug minidumps-with-heap from customers, and for those I do not see any way to get Python stack frames except for hacking up the Natvis file and then inspecting the autoInterpreterState manually.

The only option on the dumps is Debug with Native Only.

Thank you!

[gregg-miskelly]

Yes, IDumpExtension isn’t going to work correctly in your scenario as it was just designed to allow replacing a single startup engine. It would also require either re-reading the dump file yourself to decide if there is Python code loaded, or always adding Python as a choice for all dump files.

My suggestion: You don’t actually need to use the Dump Launcher page to debug dump files. So I would suggest investigating how much work it is to get dump file debugging to work, and if you think it is worth pursuing we can figure out how to get Python to show up as a choice in some future version of VS. To debug a dump file without the Dump Launcher page, you just call LaunchDebugTargets[2/3/4] as you normally would, but set the dump file as bstrExe. You can probably do this by just changing the launching command in a normal python+native interop project.

[gramster]

We have no plans to add features to native debugging; its a low-use feature so not high priority.