Mail Archives: djgpp/1997/10/19/03:48:48
I'd say the problem is that somehow the buffer is overflowed and not being
flushed...
I'm probably wrong tho...
Alexey.
J DOT Bischoff AT airbus DOT dasa DOT de wrote in article
<9710151405 DOT AA21437 AT axe DOT bre DOT da>...
> Hi!
>
> > Well the situation is the reverse! Using this code to generate the
array:
> >
> > #include <stdio.h>
> >
> > int main(int argc, char *argv[])
> > {
> > int i;
> > printf("unsigned char x[]={\n");
> > for (i=0; i<182520; i++)
> > {
> > printf("%d",i % 256);
> > if (i!=182519)
> > printf(",");
> > if ((i % 20)==19)
> > printf("\n");
> > }
> > printf("};\n");
> > return 0;
> > }
> >
> > I got "out of virtual"!!!!!, perhaps that isn't very important because
you
> > don't know what go32-v2 reports in my machine:
> >
> > DPMI memory available: 27435 Kb
> > DPMI swap space available: 130389 Kb
> >
> > So 128Mb is not enough!!
>
>
> This seems to be a general problem to all gcc-implementations (not only
djgpp).
> A example program that uses your 180000+-elements x[]-array created by
> your example code above crashed on my Unix workstation (128 MB),
> but with 256 MB it compiles well (gcc vers. 2.7.2.2).
>
> So I think this problem should be addressed to the developers of gcc.
>
>
> Jens
> --
>
- Raw text -