www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Problems with debuggers

reply "Todor Totev" <umbra.tenebris list.ru> writes:
Hi all,
I followed the advices in  =

http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments
about using WinDbg and MS visual studio to debug D programmes but I didn=
't  =

succeed.
I tried with VS2005 (both Express edition & professional).
I followed the procedure and set a breakpoint on the 1st line of main().=

When I start debugging VS gives me a message that it cannot find symbols=

so I cannot use breakppoints.
Then I tried WinDbg freshly downloaded from MS site. The same result -
it complains about missing symbols.
I double checked that I compile with -g -debug
Does anyone succeed in using those beasts to debug D programmes?
Any help will be greatly appreciated.
Regards,
Todor

As a side note, Regan Heath suggest to use post-build step for running  =

optlink.
I found that this really upsets VS IDE so I used pre-link step instead.
Todor
Feb 04 2006
next sibling parent rsl <rsl_member pathlink.com> writes:
VS2005 debugger fails breakpoint mapping for executables created by dmc/dmd.

I don't know why breakpoint setting can't works in VS2005. 
To enter break mode use asm{int 3;} or FunctionBreak like _Dmain().
once entered break mode it can debug same like VS2003.

In article <op.s4halowbihwmk4 todor-1-xp.sanbolic.local>, Todor Totev says...
Hi all,
I followed the advices in  =

http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments
about using WinDbg and MS visual studio to debug D programmes but I didn=
't  =

succeed.
I tried with VS2005 (both Express edition & professional).
I followed the procedure and set a breakpoint on the 1st line of main().=

When I start debugging VS gives me a message that it cannot find symbols=

so I cannot use breakppoints.
Then I tried WinDbg freshly downloaded from MS site. The same result -
it complains about missing symbols.
I double checked that I compile with -g -debug
Does anyone succeed in using those beasts to debug D programmes?
Any help will be greatly appreciated.
Regards,
Todor

As a side note, Regan Heath suggest to use post-build step for running  =

optlink.
I found that this really upsets VS IDE so I used pre-link step instead.
Todor

Feb 04 2006
prev sibling next sibling parent reply "Walter Bright" <newshound digitalmars.com> writes:
Microsoft's newer windbg's seem to have dropped support for codeview debug 
info. But the one that comes on the Digital Mars CD *does* work. 
Feb 04 2006
parent Hasan Aljudy <hasan.aljudy gmail.com> writes:
Walter Bright wrote:
 Microsoft's newer windbg's seem to have dropped support for codeview debug 
 info. But the one that comes on the Digital Mars CD *does* work. 
 
 

Why don't you put it online for free download? <g>
Feb 04 2006
prev sibling next sibling parent AgentOrange <AgentOrange_member pathlink.com> writes:
build with -g

In article <op.s4halowbihwmk4 todor-1-xp.sanbolic.local>, Todor Totev says...
Hi all,
I followed the advices in  =

http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments
about using WinDbg and MS visual studio to debug D programmes but I didn=
't  =

succeed.
I tried with VS2005 (both Express edition & professional).
I followed the procedure and set a breakpoint on the 1st line of main().=

When I start debugging VS gives me a message that it cannot find symbols=

so I cannot use breakppoints.
Then I tried WinDbg freshly downloaded from MS site. The same result -
it complains about missing symbols.
I double checked that I compile with -g -debug
Does anyone succeed in using those beasts to debug D programmes?
Any help will be greatly appreciated.
Regards,
Todor

As a side note, Regan Heath suggest to use post-build step for running  =

optlink.
I found that this really upsets VS IDE so I used pre-link step instead.
Todor

Feb 04 2006
prev sibling next sibling parent AgentOrange <AgentOrange_member pathlink.com> writes:
Oops, im sorry, i missed where you said you used -g, yeah just get an older dev
studio

In article <op.s4halowbihwmk4 todor-1-xp.sanbolic.local>, Todor Totev says...
Hi all,
I followed the advices in  =

http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments
about using WinDbg and MS visual studio to debug D programmes but I didn=
't  =

succeed.
I tried with VS2005 (both Express edition & professional).
I followed the procedure and set a breakpoint on the 1st line of main().=

When I start debugging VS gives me a message that it cannot find symbols=

so I cannot use breakppoints.
Then I tried WinDbg freshly downloaded from MS site. The same result -
it complains about missing symbols.
I double checked that I compile with -g -debug
Does anyone succeed in using those beasts to debug D programmes?
Any help will be greatly appreciated.
Regards,
Todor

As a side note, Regan Heath suggest to use post-build step for running  =

optlink.
I found that this really upsets VS IDE so I used pre-link step instead.
Todor

Feb 04 2006
prev sibling parent RD <sleepydude00 yahoo.co.uk> writes:
U need to set the _NT_SYMBOL_PATH. This should resolve the symbols error
Nov 09 2006