Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!gatech!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr From: sastdr@torpid.unx.sas.com (Thomas David Rivers) Subject: Building profiled libc library gets SIGSEGV? Sender: news@unx.sas.com (Noter of Newsworthy Events) Message-ID: <C5FHqr.L8t@unx.sas.com> Date: Tue, 13 Apr 1993 15:30:26 GMT Nntp-Posting-Host: torpid.unx.sas.com Organization: SAS Institute Inc. Lines: 22 Well, I just last night got around to applying the 0.2.2 patchkit; and in rebuilding libc (cd /usr/src/lib; make) I noticed that the build got a signal 11 while building the profiled C library (libc_p.a). So, I thought, I'll look and see what came with the distribution to see if anything had ever been built. It looks like all the profiling libraries are their *except* libc_p.a This isn't really a concern, since I don't plan on profiling anything too soon; but I was wondering if I'm the only one who noticed this. A signal 11 is a SIGSEGV, but Make didn't report which command got the signal, etc... - Dave Rivers - (sastdr@unx.sas.com (work)) (rivers@ponds.uucp (home)) -- UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express