Thanks for that link Steve. I will read it and see what it can help me do. It
does seem like it is pretty much on target for the scenario I have, which is a
C DLL project that is invoked by python wrapper functions invoked from a python
script.
Peter
> -Original Message-
> From:
On 16Dec2020 2114, pjfarl...@earthlink.net wrote:
If anyone has or knows of step-by-step instructions on how to set that debug
environment up and start the outer-level script with debug breakpoints in the
DLL I would greatly appreciate it. I'm also doing my own searches for
tutorials on
Thank you Emily! That may allow me to do what I need to do to find the
error(s) lurking there.
No multi-processing is involved in my current project, so it should be more
straightforward to accomplish the debugging I need to do.
Peter
From: Emily Bowman
Sent: Wednesday, December
Even if Python itself is the standard distribution, you should be able to
debug your outside DLL module in VS just by putting a breakpoint on your
favorite line and setting "/path/to/python.exe -m yourmodule" as the
command path under debugging in your project properties, or whatever
commandline
Yes, that is my specific issue. I have a C DLL invoked by a python wrapper
module using ctypes that has at least one issue (and likely more than one) so I
need to be able to start a python test script and debug the lower-level DLL
code. The C test programs for the lower-level C DLL all seen
On 2020-12-16 19:19, Paul Moore wrote:
Personally, I just have Visual Studio and VS Code as my text editor. I
rarely use Visual Studio directly, though, I mostly use the
`build.bat` and similar scripts in the `PCBuild` directory.
Having said that, I'm not doing anything like debugging problems
Personally, I just have Visual Studio and VS Code as my text editor. I
rarely use Visual Studio directly, though, I mostly use the
`build.bat` and similar scripts in the `PCBuild` directory.
Having said that, I'm not doing anything like debugging problems with
DLLs, for which I imagine a decent C
