Thread overview
DMD 0.82 is even more buggy than 0.81
Apr 01, 2004
imr1984
Apr 01, 2004
Manfred Nowak
Apr 01, 2004
imr1984
Apr 01, 2004
Stewart Gordon
Apr 01, 2004
J Anderson
Apr 01, 2004
Walter
Apr 01, 2004
Walter
Apr 02, 2004
J C Calvarese
April 01, 2004
i get the following message when compiling my project with 0.82:

Internal error: ..\ztc\cod1.c 2651

and it compiled fine with DMD 0.81. Unfortunately my project is so big that there is not way i could track down the piece of code thats causing this.


April 01, 2004
imr1984 wrote:

> my project is so big that there is not way i could track down the piece of code thats causing this.

<g> if you can compile it, then there is a way to stop that.

So long!

April 01, 2004
the thing is i cant compile it now. DMD throws up on me where it didnt before :(

In article <c4hfuu$cvc$1@digitaldaemon.com>, Manfred Nowak says...
>
>imr1984 wrote:
>
>> my project is so big that there is not way i could track down the piece of code thats causing this.
>
><g> if you can compile it, then there is a way to stop that.
>
>So long!
>


April 01, 2004
imr1984 wrote:

> the thing is i cant compile it now. DMD throws up on me where it didnt before :(
<snip>

Oh well, maybe someone'll manage to isolate the problem someday....

Stewart.

-- 
My e-mail is valid but not my primary mailbox, aside from its being the unfortunate victim of intensive mail-bombing at the moment.  Please keep replies on the 'group where everyone may benefit.
April 01, 2004
imr1984 wrote:

>the thing is i cant compile it now. DMD throws up on me where it didnt before :(
>  
>
This is probably obvious but when debugging dig (with such errors) I ran the complier in verbose mode to isolate the particular module.  Then commented out code (large at first in a kinda binary search fashion) until I worked down to the problem area.

-- 
-Anderson: http://badmama.com.au/~anderson/
April 01, 2004
"imr1984" <imr1984_member@pathlink.com> wrote in message news:c4h2vh$2qtl$1@digitaldaemon.com...
> i get the following message when compiling my project with 0.82:
>
> Internal error: ..\ztc\cod1.c 2651
>
> and it compiled fine with DMD 0.81. Unfortunately my project is so big
that
> there is not way i could track down the piece of code thats causing this.

Sure there is. Copy your project to another directory, then just start deleting code, function by function.


April 01, 2004
"J Anderson" <REMOVEanderson@badmama.com.au> wrote in message news:c4ho0k$pbk$2@digitaldaemon.com...
> imr1984 wrote:
>
> >the thing is i cant compile it now. DMD throws up on me where it didnt
before :(
> >
> >
> This is probably obvious but when debugging dig (with such errors) I ran the complier in verbose mode to isolate the particular module.  Then commented out code (large at first in a kinda binary search fashion) until I worked down to the problem area.

Yup, that's how it's done.


April 02, 2004
imr1984 wrote:
> i get the following message when compiling my project with 0.82: 
> 
> Internal error: ..\ztc\cod1.c 2651
> 
> and it compiled fine with DMD 0.81. Unfortunately my project is so big that
> there is not way i could track down the piece of code thats causing this.

I've tried tracking down errors in big projects and I know it can be frustrating.

If it's a multiple-file project, you could try compiling files separately.

Instead of:
dmd file1.d file2.d

Try this:
dmd file1.d -c
dmd file2.d -c

If the error shows up for one of the separate files, then that narrows it down.


-- 
Justin
http://jcc_7.tripod.com/d/