[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segfault with Java and "make check"
From: |
Mike Miller |
Subject: |
Re: Segfault with Java and "make check" |
Date: |
Sat, 2 Feb 2013 00:48:59 -0500 |
On Fri, Feb 1, 2013 at 6:58 PM, Rik wrote:
> I took a look at quadcc.cc and it is not recursion that is the problem. It
> simply implements some huge local variables on the stack that should
> probably be allocated from the heap instead. There is a #define in the
> code that controls how many singularities can be passed to the function.
>
> /* Define the size of the interval heap. */
> #define cquad_heapsize 200
>
> The current value is 200 which leads to ~322 kB worth of local variables on
> the stack. I think that specifying 50 singularities along an integral path
> would probably be plenty. As a quick fix, does changing line 40 of
> corefcn/quadcc.cc to 50 solve the problem?
Yes, the segfault goes away for me with that change.
--
mike
- Re: Segfault with Java and "make check", Rik, 2013/02/01
- Re: Segfault with Java and "make check", John W. Eaton, 2013/02/01
- Re: Segfault with Java and "make check", Mike Miller, 2013/02/01
- Re: Segfault with Java and "make check", Rik, 2013/02/01
- Re: Segfault with Java and "make check",
Mike Miller <=
- Re: Segfault with Java and "make check", Daniel J Sebald, 2013/02/02
- Re: Segfault with Java and "make check", Mike Miller, 2013/02/02
- Re: Segfault with Java and "make check", Daniel J Sebald, 2013/02/02
- Re: Segfault with Java and "make check", PhilipNienhuis, 2013/02/02
- Re: Segfault with Java and "make check", Daniel J Sebald, 2013/02/02
- Re: Segfault with Java and "make check", Jordi GutiƩrrez Hermoso, 2013/02/04