RE: I am getting SIGSEGV in alloca, what could be the cause ?

[Mayank Kumar <mayank at microsoft dot com>]

HI David,
But the same GNU packages compile and run well without issues with an older linker. So I am assuming that the GNU code that I am compiling would not have any error.

Thanks
Mayank


-----Original Message-----
From: David Daney [mailto:ddaney@avtrex.com]
Sent: Tuesday, September 11, 2007 11:29 PM
To: Mayank Kumar
Cc: binutils@sources.redhat.com
Subject: Re: I am getting SIGSEGV in alloca, what could be the cause ?

Mayank Kumar wrote:
> Hi
> With binutils 2.17 compiled programs on interix, I am sometimes getting crashes like
>
> +++++++++++++++++++++++++++++++++++
> Program received signal SIGSEGV, Segmentation fault.
> 0x00405f57 in _alloca () at dfa.c:1777
> 1777                  pos[j] = lastpos[j];
>
> +++++++++++++++++++++++++++++++++++
>
> Is it because the program is running out of stack space or is there some other reason.
> The crash occurs when that 2.17 linked binary is run. This occurs for some programs
> Only and not always. Any pointers in this area  would be helpful. I am trying to
> Compile GNU packages only.

Your debugger should allow you to examine registers and code so you can
figure out which address caused the fault.  If it is near a page
boundary on the stack, a stack overflow would be indicated.

David Daney