[ODE] segv with memory allocation using dALLOCA16

[Shaul Kedem]

Hi, I have a question...

How come the stack is being used so much?
In the Windows version creating a thread with very
large stack size is not recommendable.

shul

--- Russ Smith <russ at q12.org> wrote:
> 
> > It turns out that when requesting a larger then
> available memory
> > segment it still returns a non null pointer. So
> I'm guessing that's
> > whats happening and causing the seg fault (A isn't
> null when the segv
> > occurs on line 795).
> 
> that'd be my guess too. currently ODE does not fail
> gracefully when
> it runs out of stack mem.
> 
> > Is there any way to correct this?
> 
> you have nj=124, which BTW is a *lot* of joints in a
> single island.
> what is the corresponding m value? check the amount
> of memory being
> allocated for A. if you have 124 hinge joints this
> is still only
> 2.9 Mb being allocated for A (for dReal = double),
> that should fit on a
> linux stack with no problems. use getrlimit() to
> check your stack upper
> limit. does your application have a lot of mmap()s
> that might be
> crowding the stack?
> 
> russ.
> 
> --
> Russell Smith
> http://www.q12.org
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1