> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 16 July 2004 15:16
> >Yes, I see. Yhe problem is the default stack size on cygwin
> (2 MB), you
> >can increase it.
> >
> >$ gcc -o aa -Wl,--stack,8388608 aa.c
> >
> >$ ./aa
> >ok
> >
> >$ cat aa.c
> >#defi
Christopher wrote:
> On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote:
>>Pietro schrieb:
>>
>>> Gerrit,
>>
>>> I think you just did:
>>
>>> the program should print "ok" upon executing and it didn't. if you debug,
>>> say, with insight, aa.exe will bail before reaching the printf st
On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote:
>Pietro schrieb:
>
>> Gerrit,
>
>> I think you just did:
>
>> the program should print "ok" upon executing and it didn't. if you debug,
>> say, with insight, aa.exe will bail before reaching the printf statement,
>> generating a segme
Pietro schrieb:
> Gerrit,
> I think you just did:
> the program should print "ok" upon executing and it didn't. if you debug,
> say, with insight, aa.exe will bail before reaching the printf statement,
> generating a segmentation violation signal.
> let me know. thanks for looking into it.
> P
I have the following example to propose:
/** aa.c **/
#define NXY 5000
#define NXY 7000
int xy[NXY][NXY];
main(){
printf("ok\n");
}
This will work when NXY=5000, but will generate a SIGSEV exception before
reaching the first statement when NXY=7000.
The array in the faulty case is 187MB. The gcc
5 matches
Mail list logo
