Re: Stack Problem?

[petter.fryklund.konsult@dynamics.saab.se (Petter Fryklund)]

The problem was really an erronous free of an instance of a global
data array.

But for future ... what can we do about monitoring stack usage in
general. We're using several different GNAT's but this specific is
3.15 on Solaris 5.5, 5.6 or 5.8.


kcline17@hotmail.com (Kevin Cline) wrote in message news:<ba162549.0301161252.17eefbbe@posting.google.com>...
> petter.fryklund.konsult@dynamics.saab.se (Petter Fryklund) wrote in message news:<f74cb448.0301160210.3fa1bd66@posting.google.com>...
> > We are getting a SEGV out of realfree (/libc.so.1) call stack is
> > 
> > realfree
> > cleanfree
> > _malloc_unlocked
> > malloc
> > calloc
> > netconfig_dup
> > __rpc_getconfigip
> > gethostbyname_r
> > gnat__sockets__get_host_by_name
> > ....
> > 
> > Parameters sent from gnat__... seems to be alright. I've no idea about
> > the library, since it's not compiled with debug info.
> > 
> > I suspect that we've exceed the stack limit, but I can't find a way to
> > verify that. 
> 
> Crashes below malloc are almost always caused by heap
> corruption.  Your code or some library code has probably corrupted 
> the heap by freeing the same object twice, or by modifying an object
> after it was deallocated.