"Mark Phillips" <[EMAIL PROTECTED]> writes:
> Thanks for this! I increased the stack size via "ulimit -s "
> and the thick4 executable no longer crashes.
>
> However the curious thing is that with test.c, I thought "surely by
> increasing N I could make it seg fault too" but I can't, even
>
> #d
Peter Kovacs [EMAIL PROTECTED] wrote:
> The problem is: you're simply asking for too much stack space. On my
> machine, ulimit -s reports 8129 (that's in Kilobytes). When I write a
> seperate program such as:
>
> #include
>
> void main(int argc, char **argv)
> {
> double a[209677];
>
I just compiled it with gcc 2.95 and it compiled
and ran fine..
very strange
xucaen
--- Mark Phillips <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I thought I'd found a gcc compiler error (and
> still may have). The
> following program crashes with a segmentation
> fault.
>
> #define N 209677
>
>
also sprach Mark Phillips (on Wed, 07 Mar 2001 03:18:56AM +1030):
> -rwxrwxr-x1 mark mark 4731 Mar 7 02:53 test*
> -rw-rw-r--1 mark mark 162 Mar 7 02:53 test.c
> -rwxrwxr-x1 mark mark 4733 Mar 7 02:53 thick4*
> -rw-r--r--1 mark mark
I don't think this is a GCC error because gcc compiles this program
successfully.
The problem is: you're simply asking for too much stack space. On my
machine, ulimit -s reports 8129 (that's in Kilobytes). When I write a
seperate program such as:
#include
void main(int argc, char **argv)
{
5 matches
Mail list logo