Has anyone been able to debug with VS2005?

Bill Baxter dnewsgroup at billbaxter.com
Fri Nov 17 22:54:21 PST 2006

Carlos Santander wrote:
> Jim Hewes escribió:
>> Thanks, I'll check out the plug-in when dsource is back.
>> I was able to debug the sample hello.exe app in VS2005 by doing the 
>> following:
>> 1. Load hello.exe into VS2005 as a project. Also, open the hello.d 
>> source file.
>> 2. Press F11 to take one step into the code. Source is not available, 
>> so show disassembly.
>> 3. In the disassembly window, enter the address as "_Dmain" and hit 
>> return. The window will show the mixed source/assembly at _Dmain.
>> 4. In the disassembly window, set a breakpoint at the first line of 
>> _Dmain and hit Go.
>> 5. In the source window, you should now see execution stop at the 
>> first line and you can single step from there.
>> However, I wasn't able to set breakpoints from the source window. But 
>> I haven't had much time to play with it yet. Hopefuly I can spend more 
>> time next weekend. (Hey! I have a day job.)
>> Jim
> You have to compile with -g to do so.

Nope.  Setting breakpoints on source file lines still doesn't work even 
with -g.

But something's odd.  I'm pretty sure it _did_ work before I installed 
the VSPluginD.  I could set breakpoints, but I couldn't see variables 
before.  Now I can see variables, but I can't set breakpoints (except 
from dissasembly).  Or maybe it was only VS.NET 7.1 that was able to set 
source-level breakpoints?

I wonder if it's possible to tweak something in AutoExp.dat or in an 
EEAddIn plugin to make D strings and such show up properly, without the 
need for the "(char*)*((int*)(&str)+1)" trick.

The debugger seems to think all D arrays are of type unsigned__int64, 
though, which will probably be problematic.


More information about the Digitalmars-d-learn mailing list