From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d29352214f90bc6f
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-01-16 12:52:04 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: kcline17@hotmail.com (Kevin Cline)
Newsgroups: comp.lang.ada
Subject: Re: Stack Problem?
Date: 16 Jan 2003 12:52:04 -0800
Organization: http://groups.google.com/
Message-ID: <ba162549.0301161252.17eefbbe@posting.google.com>
References: <f74cb448.0301160210.3fa1bd66@posting.google.com>
NNTP-Posting-Host: 192.76.54.20
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1042750324 3502 127.0.0.1 (16 Jan 2003 20:52:04
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 16 Jan 2003 20:52:04 GMT
Xref: archiver1.google.com comp.lang.ada:33104
Date: 2003-01-16T20:52:04+00:00
List-Id: <comp.lang.ada>

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.