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 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-21 09:24:25 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: petter.fryklund.konsult@dynamics.saab.se (Petter Fryklund) Newsgroups: comp.lang.ada Subject: Re: Stack Problem? Date: 21 Jan 2003 09:24:25 -0800 Organization: http://groups.google.com/ Message-ID: References: NNTP-Posting-Host: 138.14.239.132 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1043169865 18458 127.0.0.1 (21 Jan 2003 17:24:25 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 21 Jan 2003 17:24:25 GMT Xref: archiver1.google.com comp.lang.ada:33302 Date: 2003-01-21T17:24:25+00:00 List-Id: "David C. Hoos, Sr." wrote in message news:... > Have you followed the instructions in the GNAT User's Guide, section 3.2.6? Yes, I feel that we have. > > ----- Original Message ----- > From: "Petter Fryklund" > Newsgroups: comp.lang.ada > To: > Sent: January 20, 2003 4:05 AM > Subject: Re: Stack Problem? > > > > 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:... > > > petter.fryklund.konsult@dynamics.saab.se (Petter Fryklund) wrote in message > news:... > > > > 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. > > _______________________________________________ > > comp.lang.ada mailing list > > comp.lang.ada@ada.eu.org > > http://ada.eu.org/mailman/listinfo/comp.lang.ada > > > >