"Ben Hinkle" <ben.hinkle@gmail.com> wrote in message news:d4t9f3$np4$1@digitaldaemon.com...
>
> "Walter" <newshound@digitalmars.com> wrote in message news:d4spqt$28e$1@digitaldaemon.com...
> >
> > "zwang" <nehzgnaw@gmail.com> wrote in message news:d4rvhm$24gn$1@digitaldaemon.com...
> >> I can step through the code using windbg without a problem. The problem is
> > that
> >> no local variables are resolved without a .pdb file, and I can't
inspect
> > any
> >> value in the "Watch" window.
> >
> > I use windbg.exe 5.1, and doing a "locals" window shows them just fine. There's no .pdb file.
>
> Funny, like zwang I've never gotten any locals either. I'm also using 5.1 and compiling with -g. I get stack traces and can step through code but that's it.

Try using the windbg.exe that comes on the Digital Mars CD.

On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:

> Try using the windbg.exe that comes on the Digital Mars CD.

Are you saying that the CD windbg.exe is different to the one distributed by Microsoft?

-- 
Derek Parnell
Melbourne, Australia
30/04/2005 10:20:33 AM

"Derek Parnell" <derek@psych.ward> wrote in message news:p2dioncv1dp2.v3yv2de6beka.dlg@40tude.net...
> On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:
>
> > Try using the windbg.exe that comes on the Digital Mars CD.
>
> Are you saying that the CD windbg.exe is different to the one distributed by Microsoft?

The one on the CD is:

08/08/1996  08:30 PM           559,888 WINDBG.EXE

which is Microsoft's one. However, based on the information in this thread, Microsoft has likely changed it to the point where it won't work anymore with Microsoft Codeview 4 symbolic debug info. I've stuck with CV4 format because it's the last one that Microsoft officially documented.

On Fri, 29 Apr 2005 17:58:54 -0700, Walter wrote:

> "Derek Parnell" <derek@psych.ward> wrote in message news:p2dioncv1dp2.v3yv2de6beka.dlg@40tude.net...
>> On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:
>>
>>> Try using the windbg.exe that comes on the Digital Mars CD.
>>
>> Are you saying that the CD windbg.exe is different to the one distributed by Microsoft?
> 
> The one on the CD is:
> 
> 08/08/1996  08:30 PM           559,888 WINDBG.EXE
> 
> which is Microsoft's one. However, based on the information in this thread, Microsoft has likely changed it to the point where it won't work anymore with Microsoft Codeview 4 symbolic debug info. I've stuck with CV4 format because it's the last one that Microsoft officially documented.

Yep, yours is a different one. The current version is dated 18/May/2004 and is 343KB long. Don't suppose you could make your edition available for free?

-- 
Derek Parnell
Melbourne, Australia
30/04/2005 11:10:57 AM

>> > I use windbg.exe 5.1, and doing a "locals" window shows them just fine. There's no .pdb file.
>>
>> Funny, like zwang I've never gotten any locals either. I'm also using 5.1 and compiling with -g. I get stack traces and can step through code but that's it.
>
> Try using the windbg.exe that comes on the Digital Mars CD.

done. anything for a debugger :-)
plus I'm sure the other stuff on there will be useful, too...

I think, the one on the CD is an old windbg (perhaps version 5.1 from about 1998?) which is not easy to obtain today. I could not find such an old version of this ms tool (in an 4h search) - and wouldn't buy the D CD for $45 only to get this buggy (so has been written) ms tool; today they only distribute some 6.x versions over their webpage (which only understand pdb).

BUT: I checked the open-watcom tools distributed with a graphical debugger which works fine for D (http://www.openwatcom.org/). The complete package comes with a debugger and several other tools as a 64Mb download. Having a good debugger is an important feature for D so I think I should hind to this probably "competitive" piece of software. Perhaps, there will be a more D way of debugging in the future ;-) .

You can debug /without/ graphical code interaction but /with/ the possibility to set breakpoints on functions (use the module window clicking right on modules) and variable assignments (use the locale window clicking right on symbols) and so on ... I think it is not possible to graphically interact with the code because of mangling but it is convenient to step in the assembler window. The graphical debugger is the "wdw.exe" in the binnt directory.

BUT: the gdb command line debugger under Cygwin seems to be the best debugger for windows D development. Unfortunately, -- but hopefully soon -- the new gcd (gdc 0.11 ^= dmd 0.121) has not been "integrated" in the Cygwin distribution (it is a major operation to recompile gcc from source under Cygwin). I think (hope) the maintainers will make it for us available soon.

Martin

Derek Parnell wrote:
> On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:
> 
> 
>>Try using the windbg.exe that comes on the Digital Mars CD.
> 
> 
> Are you saying that the CD windbg.exe is different to the one distributed
> by Microsoft?
> 

The watcom debugger described in my former mail does not interact with the code but the correct code line numbers are displayed in the source window so you can set break points on line numbers (where the watcom dbg says "Unable to open source file") with the assistance of an external editor.

With observing locales and "watches" I think this is quite a complete debugger for D.

Martin

Martin Boeker wrote:
> I think, the one on the CD is an old windbg (perhaps version 5.1 from about 1998?) which is not easy to obtain today. I could not find such an old version of this ms tool (in an 4h search) - and wouldn't buy the D CD for $45 only to get this buggy (so has been written) ms tool; today they only distribute some 6.x versions over their webpage (which only understand pdb).
> 
> BUT: I checked the open-watcom tools distributed with a graphical debugger which works fine for D (http://www.openwatcom.org/). The complete package comes with a debugger and several other tools as a 64Mb download. Having a good debugger is an important feature for D so I think I should hind to this probably "competitive" piece of software. Perhaps, there will be a more D way of debugging in the future ;-) .
> 
> You can debug /without/ graphical code interaction but /with/ the possibility to set breakpoints on functions (use the module window clicking right on modules) and variable assignments (use the locale window clicking right on symbols) and so on ... I think it is not possible to graphically interact with the code because of mangling but it is convenient to step in the assembler window. The graphical debugger is the "wdw.exe" in the binnt directory.
> 
> BUT: the gdb command line debugger under Cygwin seems to be the best debugger for windows D development. Unfortunately, -- but hopefully soon -- the new gcd (gdc 0.11 ^= dmd 0.121) has not been "integrated" in the Cygwin distribution (it is a major operation to recompile gcc from source under Cygwin). I think (hope) the maintainers will make it for us available soon.
> 
> Martin
> 
> Derek Parnell wrote:
> 
>> On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:
>>
>>
>>> Try using the windbg.exe that comes on the Digital Mars CD.
>>
>>
>>
>> Are you saying that the CD windbg.exe is different to the one distributed
>> by Microsoft?
>>

In article <d4spqt$28e$1@digitaldaemon.com>, Walter says...
>
>
>"zwang" <nehzgnaw@gmail.com> wrote in message news:d4rvhm$24gn$1@digitaldaemon.com...
>> I can step through the code using windbg without a problem. The problem is
>that
>> no local variables are resolved without a .pdb file, and I can't inspect
>any
>> value in the "Watch" window.
>
>I use windbg.exe 5.1, and doing a "locals" window shows them just fine. There's no .pdb file.

Maybe that's something more recent versions want?  I haven't used WinDbg in a while, but I don't remember being able to view variables by name.  I'll have to grab 5.1 and try it out.


Sean

Code is displayed in the debugger source window if the source path is correctly set in the file dialog. It has to be set to the directory which holds the D files (can't be done in the dialogue "browse" which selects single files).

Martin

Martin Boeker wrote:
> The watcom debugger described in my former mail does not interact with the code but the correct code line numbers are displayed in the source window so you can set break points on line numbers (where the watcom dbg says "Unable to open source file") with the assistance of an external editor.
> 
> With observing locales and "watches" I think this is quite a complete debugger for D.
> 
> Martin
> 
> Martin Boeker wrote:
> 
>> I think, the one on the CD is an old windbg (perhaps version 5.1 from about 1998?) which is not easy to obtain today. I could not find such an old version of this ms tool (in an 4h search) - and wouldn't buy the D CD for $45 only to get this buggy (so has been written) ms tool; today they only distribute some 6.x versions over their webpage (which only understand pdb).
>>
>> BUT: I checked the open-watcom tools distributed with a graphical debugger which works fine for D (http://www.openwatcom.org/). The complete package comes with a debugger and several other tools as a 64Mb download. Having a good debugger is an important feature for D so I think I should hind to this probably "competitive" piece of software. Perhaps, there will be a more D way of debugging in the future ;-) .
>>
>> You can debug /without/ graphical code interaction but /with/ the possibility to set breakpoints on functions (use the module window clicking right on modules) and variable assignments (use the locale window clicking right on symbols) and so on ... I think it is not possible to graphically interact with the code because of mangling but it is convenient to step in the assembler window. The graphical debugger is the "wdw.exe" in the binnt directory.
>>
>> BUT: the gdb command line debugger under Cygwin seems to be the best debugger for windows D development. Unfortunately, -- but hopefully soon -- the new gcd (gdc 0.11 ^= dmd 0.121) has not been "integrated" in the Cygwin distribution (it is a major operation to recompile gcc from source under Cygwin). I think (hope) the maintainers will make it for us available soon.
>>
>> Martin
>>
>> Derek Parnell wrote:
>>
>>> On Fri, 29 Apr 2005 14:12:23 -0700, Walter wrote:
>>>
>>>
>>>> Try using the windbg.exe that comes on the Digital Mars CD.
>>>
>>>
>>>
>>>
>>> Are you saying that the CD windbg.exe is different to the one distributed
>>> by Microsoft?
>>>