This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Weird startup issue with -fsplit-stack


On Tue, May 20, 2014 at 10:30 PM, Dmitry Antipov <dmantipov@yandex.ru> wrote:
>
> The next major problem is that -fsplit-stack code randomly crashes with the
> useless gdb backtrace, usually pointing to the very beginning of the
> function
> (plus occasional "Cannot access memory at..." messages), e.g.:
>
> (gdb) bt 1
> #0  0x00000000005a615b in mark_object (arg=0) at
> ../../trunk/src/alloc.c:6039
>
>      6037  void
>      6038  mark_object (Lisp_Object arg)
> ==>  6039  {
>
> IIUC this usually (with traditional stack) happens due to stack overflow.
> But what may be the case with -fsplit-stack? I do not receive any error
> messages from libgcc, and there are a lot of free heap memory. If that
> matters,
> mark_object is recursive, and recursion depth may be very high, up to a few
> tens of thousands calls.

I'm sorry, I have nothing useful to suggest.  I agree that that sounds
like a stack overflow, which should in general be impossible with
-fsplit-stack when using the gold linker.  I don't know what is
happening here.  I've tested with massive recursion so I don't think
that is the problem by itself.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]