Visual studio has a nasty habit of dropping build products into the source directory, it is an awful policy but easily defeated.
Is there a way to attach to a process with the Inspector product? The problem is that currently I run the inspector by setting the debug and working directories tot he install location and then start the inspect wizard.
Other than the annoying "code has been modified" warning, this seems to work. But after the demo was up and I bought a copy, I do see a lot of cases where it cannot find the source as "it has no stack frames".
I have been taking this to mean the object destructed by the time the inspector ran, but could it be the running it out of the install directory? This is a real program and it requires all the stuff from the install. It seems like I might be doing something wrong, this feels klugey