Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!news2.acs.oakland.edu!condor.ic.net!news.sojourn.com!cancer.vividnet.com!hunter.premier.net!news.mathworks.com!news-peer.gsl.net!news.gsl.net!portc01.blue.aol.com!newsstand.cit.cornell.edu!news.acsu.buffalo.edu!news.drenet.dnd.ca!crc-news.doc.ca!nott!bcarh189.bnr.ca!bmerhc5e.bnr.ca!news From: Andrew Atrens <atrens@bnr.ca> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Is libc.so.3.0 broken? Date: Wed, 02 Oct 1996 13:59:26 -0400 Organization: Bell Northern Research Lines: 32 Message-ID: <3252AD7E.3FF5@bnr.ca> NNTP-Posting-Host: bmerh278.bnr.ca Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (X11; I; HP-UX A.09.05 9000/712) Hi again folks, I'm running the August 1 SNAP and I've got a problem :( I've been using the AUIS distribution for quite some time ( > year ). During this period I've rebuilt it a few times from scratch, each time without a hitch. Last week, however, I wasn't as lucky. The distribution would build, but only a few of the applications would work correctly. The rest instantly core dump on SIG 11, SIG 10, and even SIG 8. Analysis of the cores with GDB indicates that the faults occur in 'cerror' which is a little assembly function inside libc. With a bit of trickery I managed to selectively link a few applications against libc.so.2.2 ( actually the .a equivalent but you know what I mean ), these worked flawlessly as before. So the obvious conclusion is that something has changed/is broken in libc.so.3.0 ( and its '.a' static equivalent ). Has anyone else encountered this? And if so, is there a clean workaround? As always any/all thoughts, suggestions, pointers and opinions would be appreciated. Cheers, Andrew. ( opinions are mine, not those of Nortel )