is there anyway to step through a program viewing the high level source code like you can in MSVC ? I tried windbg.exe but all it gave me was cryptic assembly code and register values.

imr1984 wrote:
> is there anyway to step through a program viewing the high level source code
> like you can in MSVC ? I tried windbg.exe but all it gave me was cryptic
> assembly code and register values.
> 

We're working on it in Eclipse.  I'm trying to use Eclipse 3.0 M6 and the CDT 2.0 M6 - with DMD, DM Make, and (not sure about debugger yet - cygwin, windbg, ??)

See the Eclipse Plugin thread.

Brad

imr1984 wrote:
> is there anyway to step through a program viewing the high level source code like you can in MSVC ? I tried windbg.exe but all it gave me was cryptic assembly code and register values.

To use windbg, you have to:
1. compile your program with '-g'
2. open windbg
3. open the executable (ctrl-e)
4. open the source code file(s) (ctrl-o)
5. set the breakpoints (if any)
6. run the program (step by step or until a line or...)
note that there's no information about variables and such (something about
missing a pdb file or something like that)

-----------------------
Carlos Santander Bernal

cheers for that carlos. But i just figured out how to debug D programs using Visual Studio .NET. You go into the task manager under XP and select the task and press debug. then itll open up .NET with a new solution and you can add your d source files. Brilliant :)

only one problem though - whenever i 'step into' a function, an exception is thrown.

Does anyone else have this problem?

In article <c0rmgi$162g$1@digitaldaemon.com>, Carlos Santander B. says...
>
>imr1984 wrote:
>> is there anyway to step through a program viewing the high level source code like you can in MSVC ? I tried windbg.exe but all it gave me was cryptic assembly code and register values.
>
>To use windbg, you have to:
>1. compile your program with '-g'
>2. open windbg
>3. open the executable (ctrl-e)
>4. open the source code file(s) (ctrl-o)
>5. set the breakpoints (if any)
>6. run the program (step by step or until a line or...)
>note that there's no information about variables and such (something about
>missing a pdb file or something like that)
>
>-----------------------
>Carlos Santander Bernal
>
>