Charles wrote:
> It still needs work , right now just run it on a faulty program to see a
> call stack dump.
> 
> http://www.thecodebase.com/DMDebugApi.zip
> 
> DMDebugApi\DMDebugLib.dsw is the workspace.
> 
> Youll need latest windows SDK , and MSVC6 ( or 7 if you can get it
> working ).
> 
> Eric I know you've been researching dynamic libs / OMF / COFF etc, would you
> have time to work on this ?  If so maybe we can move discussion to DSP
> forums.

Charles,
  I'll give your debugger a solid look sometime later on this week. However, I won't be able to do anything productive coding wise to it as I don't have MSVC6 installed (used to, but that was my last machine).

I'd love to help your efforts via my current research, if that's what you need.  Besides, its all quite synergistic as I could use a good debugging tool for what I'm working on.

So far I have an open OMF parser (no linker yet) that's yours to hack up all you like; its a frightful mess, but it can dump DMD's OMF files pretty well.  Its currently in the DSP SVN repos.

What I cannot fathom is how runtime object loading and linking interacts with debug information.  Right now, I feel like I run the risk of breaking debug info via runtime linking due to ignorance;  that's a drawback that is simply unacceptable.

Anyway, feel free to run amok in the DSP forum on dsource for any questions and issues you think I might be able to answer (I'd like to keep it in the forum, so it can stand as a research resource).

-- 
- EricAnderton at yahoo

Chuck.Esterbrook /at/ gmail /dot/ com wrote:
> Another idea is to write a D-to-D translator. That would be even easier since
> the target language is identical (or in the case of language changes,
> near-identical). The generated D would look different from the original source
> to the extent that debugging aids were turned on and language features had been
> tweaked.

I've thought about something like that myself.  Sort of like an aspect-oriented template for a whole source tree, eh?  Composed in an abstract fashion, it could be a very versatile tool in its own right.

> Although I feel a little silly proprosing something I don't have time to work
> on. :-)  

Hey, if you've got an hour, just throw a crude specification up on the Wiki with "please edit me if you want to contribute" plastered all over it.  Odds are you're probably a few more thoughts ahead of the rest of us on that idea.

Besides, this newsgroup is positively dreadful for archiving good concepts (as our debugger debacle has demonstrated).

> However, I've read references to a D front end. Is that in D?

I've done some hacking there myself.  Its a funny thing: its written in C, but most of that code are thinly veiled D-isms.  Picking through the source, one gets an impression of why Walter started D in the first place.  Eventually, some brave soul will convert this over to D and will likely see that its a fairly straightforward task.

-- 
- EricAnderton at yahoo

I'm using Visual Studio 2003, and Open Watcom Debugger 1.3.
VS is unable show any compound variables, Watcom is able, but for some
unknown reason to me, Watcom shows different (improper) float values.

Here's a link to a VS solution and project - you can build and debug D in VS
with that.
(If you want to add new file, add it manually by modifying .vcproj <Files>
section.
And of course, you have to modify the path to dmd.exe, if needed.)

http://elfqt.simeis.hu/szallit/D/D_VS_sampleSln.zip

(By the way, I also managed to port the first five DirectX D3D tutorials to D. If anyone interested, let me know and I will upload.)

ElfQT

"Chuck.Esterbrook /at/ gmail /dot/ com" <Chuck.Esterbrook_member@pathlink.com> wrote in message news:dds1ei$2ff9$1@digitaldaemon.com...
> What debuggers, if any, are people actually using with their DMD programs
on
> Windows? You know: setting breakpoints, examining a live stack when an
error
> occurs, etc.
>
> Does the one with DMC work with DMD executables? http://www.digitalmars.com/ugr/chapter23.html
>
>
> Thanks,
> -Chuck
>
>

> I'd love to help your efforts via my current research, if that's what you need.  Besides, its all quite synergistic as I could use a good debugging tool for what I'm working on.

That'd be great ( good word syngery  ).

> So far I have an open OMF parser (no linker yet) that's yours to hack up all you like; its a frightful mess, but it can dump DMD's OMF files pretty well.  Its currently in the DSP SVN repos.

Very cool , checking it out .

> What I cannot fathom is how runtime object loading and linking interacts with debug information.

I have a vague idea -- something about storing a pointer to a debug table ... ( mutter ... trail off ).

> Anyway, feel free to run amok in the DSP forum on dsource for any questions and issues you think I might be able to answer (I'd like to keep it in the forum, so it can stand as a research resource).

Aye sounds good!

Charlie

"pragma" <EricAnderton@youknowthedrill.yahoo> wrote in message news:dducul$1mm6$1@digitaldaemon.com...
> Charles wrote:
> > It still needs work , right now just run it on a faulty program to see a call stack dump.
> >
> > http://www.thecodebase.com/DMDebugApi.zip
> >
> > DMDebugApi\DMDebugLib.dsw is the workspace.
> >
> > Youll need latest windows SDK , and MSVC6 ( or 7 if you can get it
> > working ).
> >
> > Eric I know you've been researching dynamic libs / OMF / COFF etc, would
you
> > have time to work on this ?  If so maybe we can move discussion to DSP forums.
>
> Charles,
>    I'll give your debugger a solid look sometime later on this week.
> However, I won't be able to do anything productive coding wise to it as
> I don't have MSVC6 installed (used to, but that was my last machine).
>
> I'd love to help your efforts via my current research, if that's what you need.  Besides, its all quite synergistic as I could use a good debugging tool for what I'm working on.
>
> So far I have an open OMF parser (no linker yet) that's yours to hack up all you like; its a frightful mess, but it can dump DMD's OMF files pretty well.  Its currently in the DSP SVN repos.
>
> What I cannot fathom is how runtime object loading and linking interacts with debug information.  Right now, I feel like I run the risk of breaking debug info via runtime linking due to ignorance;  that's a drawback that is simply unacceptable.
>
> Anyway, feel free to run amok in the DSP forum on dsource for any questions and issues you think I might be able to answer (I'd like to keep it in the forum, so it can stand as a research resource).
>
> --
> - EricAnderton at yahoo

killer! ive been working on a debugger written in d since my visual studio began crashing and i got tired of re-installing it (again)...

thanks very much for this code, you just saved me some work. im going to convert some of it to d since im never going to write c++ again unless i absolutely have to


Charles wrote:
> It still needs work , right now just run it on a faulty program to see a
> call stack dump.
> 
> http://www.thecodebase.com/DMDebugApi.zip
> 
> DMDebugApi\DMDebugLib.dsw is the workspace.
> 
> Youll need latest windows SDK , and MSVC6 ( or 7 if you can get it
> working ).
> 
> Eric I know you've been researching dynamic libs / OMF / COFF etc, would you
> have time to work on this ?  If so maybe we can move discussion to DSP
> forums.
> 
> Charlie
> 
> "Charles" <noone@nowhere.com> wrote in message
> news:ddsufj$atb$1@digitaldaemon.com...
> 
>>I have been working on a Debugger for months , but have been strapped for
>>time lately ( like all of us. ).  It uses dbghelp & imghelp to extract
>>symbols.  What its missing is the ability to get 'type' info from
> 
> variables
> 
>>so it can 'see' their contents , however Walter  said he'd totally add
> 
> this
> 
>>into the debug info , soon as their codes are figured out.
>>
>>What I have now is really rough , its a mess in fact . I will clean it up
>>today and put it on the web, but I want to post while everyone is still
>>interested.
>>
>>Maybe if we all combine what little time we have we can finish it and get
> 
> a
> 
>>debugger !
>>
>>
>>Charlie
>>
>>
>>"pragma" <pragma_member@pathlink.com> wrote in message
>>news:ddsrcu$7f9$1@digitaldaemon.com...
>>
>>>In article <ddsm6e$21n$1@digitaldaemon.com>, Ben Hinkle says...
>>>
>>>>>I've received substantial benefits from:
>>>>>- Python's dumping of the entire stack trace for uncaught exceptions.
>>
>>This
>>
>>>>>really helps diagnosis.
>>>>
>>>>Someone started working on this but I don't know the current status:
>>>>http://www.digitalmars.com/d/archives/digitalmars/D/22562.html
>>>>http://www.digitalmars.com/d/archives/digitalmars/D/22967.html
>>>>
>>>>
>>>
>>>Did he ever post anything (a zip, URL, anything) to the DNG for his
> 
> work?
> 
>>Maybe
>>
>>>someone should hunt down his email?
>>>
>>>- EricAnderton at yahoo
>>
>>
> 
> 

On Tue, 16 Aug 2005 23:04:47 +0800, zwang <nehzgnaw@gmail.com> wrote:

>Chuck.Esterbrook /at/ gmail /dot/ com wrote:
>> What debuggers, if any, are people actually using with their DMD programs on Windows? You know: setting breakpoints, examining a live stack when an error occurs, etc.
>> 
>> Does the one with DMC work with DMD executables? http://www.digitalmars.com/ugr/chapter23.html
>> 
>> 
>> Thanks,
>> -Chuck
>> 
>> 
>
>I used MSVC6 and OpenWatcom Windows debugger before I wrote up a logging module plus a testing framework which enabled me to locate bugs quickly without the need of a full-fledged debugger.

Would you care to share your logging module and testing framework?

And regardless, can you say what your testing framework provides that the unittest { } feature does not?

Thanks,
Chuck

On Wed, 17 Aug 2005 00:14:13 -0700, pragma <EricAnderton@youknowthedrill.yahoo> wrote:

>Chuck.Esterbrook /at/ gmail /dot/ com wrote:
>> Another idea is to write a D-to-D translator. That would be even easier since the target language is identical (or in the case of language changes, near-identical). The generated D would look different from the original source to the extent that debugging aids were turned on and language features had been tweaked.
>
>I've thought about something like that myself.  Sort of like an aspect-oriented template for a whole source tree, eh?  Composed in an abstract fashion, it could be a very versatile tool in its own right.
>
>> Although I feel a little silly proprosing something I don't have time to work on. :-)
>
>Hey, if you've got an hour, just throw a crude specification up on the Wiki with "please edit me if you want to contribute" plastered all over it.  Odds are you're probably a few more thoughts ahead of the rest of us on that idea.
>
>Besides, this newsgroup is positively dreadful for archiving good concepts (as our debugger debacle has demonstrated).
>
> > However, I've read references to a D front end. Is that in D?
>
>I've done some hacking there myself.  Its a funny thing: its written in C, but most of that code are thinly veiled D-isms.  Picking through the source, one gets an impression of why Walter started D in the first place.  Eventually, some brave soul will convert this over to D and will likely see that its a fairly straightforward task.

I was doing some poking around the news archives and found that someone already has a d2d translator!

http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/26468 http://languagemachine.sourceforge.net/

I haven't tried it out yet, but thought I would add mention of it to this thread.

-Chuck