www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Debugger

reply ElfQT <ElfQT_member pathlink.com> writes:
Hi there.
I'd like to come back to tackle with D.
But I left some time ago in absence of a debugger. (Not just line numbers, but
watching D and other custom variables/classes.)
I did and still do wonder why that doesn't so clearly missing for other D
programmers.
I've searched the news, but haven't find any progress on the issue.
Is there any advancement, or plan on Walters part on a debugger or debugger
support?
Mar 22 2006
next sibling parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
ElfQT wrote:


 But I left some time ago in absence of a debugger. (Not just line numbers, but
 watching D and other custom variables/classes.)
 I did and still do wonder why that doesn't so clearly missing for other D
 programmers.


GDB works somewhat OK for debugging GDC...
(still has some namemangling troubles, etc)

Did you try the page on Wiki4D, for Windows ?
http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments

--anders
Mar 22 2006
parent ElfQT <ElfQT_member pathlink.com> writes:
Did you try the page on Wiki4D, for Windows ?
http://www.prowiki.org/wiki4d/wiki.cgi?DebugEnvironments


Well, last year I made a VS sample project for debugging D, so yes, I've been
there. All these very basic debugging solutions are far from adeqate.
AFAIK from last year the problem lies in the debugging info D compiler does not
provide.

(Something that would substitute a real debugger is a mind boggingly good,
built-in, configurable tracer. I'd vote for debugging.)

Thanks,
ElfQT
Mar 22 2006
prev sibling parent reply =?iso-8859-1?q?Knud_S=F8rensen?= <12tkvvb02 sneakemail.com> writes:
Do you write your unit test first ??? and what is your unit test coverage ??

On Wed, 22 Mar 2006 15:36:34 +0000, ElfQT wrote:


 Hi there.
 I'd like to come back to tackle with D.
 But I left some time ago in absence of a debugger. (Not just line numbers, but
 watching D and other custom variables/classes.)
 I did and still do wonder why that doesn't so clearly missing for other D
 programmers.
 I've searched the news, but haven't find any progress on the issue.
 Is there any advancement, or plan on Walters part on a debugger or debugger
 support?
Mar 22 2006
next sibling parent "Todor Totev" <umbra.tenebris list.ru> writes:
Last project I had to write is a windows service with one single purpose  
in life -
to craft some resources and immediatelly give them to a device driver.
Excuse me but how I am supposed to track the problems with a driver that
even does not yet exists with unit testing?
The problem is that unit testing can give you information about the fact  
that
a problem exists. But it didn't give you the state of the programs
(yes, plural case) that caused the problems!
And of cource unit testing as good as the cases you put in it.
Besides that project was quite easy to implement in C++ - I included a  
header
that gives me a infrastructure for writing Windows swervices, included a  
header
that gives me a nice wrapper for thread controlling and I wrote it in less
than 20 minutes. I wandered how much time will I need to write all this in  
D.
The D problem other than lack of debugger is that I immediatelly lose all  
that
nice C++ libraries I use everyday and thus I'm set back about 27 man-years.
Not a very exciting proposition for me. Actually for me is quicker to use  
C++
than to write/test/debug/document all that supporting code in D and after  
that
start writing something that solves the problem at hand.
Regards,
Todor



 Do you write your unit test first ??? and what is your unit test  
 coverage ??


 Hi there.
 I'd like to come back to tackle with D.
 But I left some time ago in absence of a debugger. (Not just line  
 numbers, but
 watching D and other custom variables/classes.)
 I did and still do wonder why that doesn't so clearly missing for other  
 D
 programmers.
 I've searched the news, but haven't find any progress on the issue.
 Is there any advancement, or plan on Walters part on a debugger or  
 debugger
 support?
Mar 22 2006
prev sibling parent reply ElfQT <ElfQT_member pathlink.com> writes:
Do you write your unit test first ??? and what is your unit test coverage ??


I think I know what you are trying to say.
1. No, I don't write any unit test when I am experimenting with something like
direct3d in d. It's a hard issue even in c++ and the problems can be found more
easily with debugging. Now It's even hard to check the value of a float. Show me
a d3d project / 3d engine on directx or opengl using good unit test coverage...

2. Almost the same problem when you are still learning D and have
newbie/incredible/D bug/ghost errors. You can write tons of unit test instead of
a simple debugging and variable watch.

3. Please don't try to force your developement method on me or anyone. I'm all
into unit test, but they are not for everything.
Mar 23 2006
parent =?iso-8859-1?q?Knud_S=F8rensen?= <12tkvvb02 sneakemail.com> writes:
You were wondering if others where missing good debugger support.
With good unit testing your dramatic reduce the use of a debugger.
That might be why others don't need it.

I prefers unit test over debugger session 
because unit test you can keep while debugger session 
is wasted time if you make changes to your code at a later date. 
 


On Thu, 23 Mar 2006 10:01:24 +0000, ElfQT wrote:


Do you write your unit test first ??? and what is your unit test coverage ??


 I think I know what you are trying to say.
 1. No, I don't write any unit test when I am experimenting with something like
 direct3d in d. It's a hard issue even in c++ and the problems can be found more
 easily with debugging. Now It's even hard to check the value of a float. Show
me
 a d3d project / 3d engine on directx or opengl using good unit test coverage...
 
 2. Almost the same problem when you are still learning D and have
 newbie/incredible/D bug/ghost errors. You can write tons of unit test instead
of
 a simple debugging and variable watch.
 
 3. Please don't try to force your developement method on me or anyone. I'm all
 into unit test, but they are not for everything.
Mar 23 2006