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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6e10dbd84b94a267 X-Google-Attributes: gid103376,public From: Simon Wright Subject: Re: GNAT Compilation Problems Date: 1996/09/23 Message-ID: #1/1 X-Deja-AN: 185094022 x-nntp-posting-host: pogner.demon.co.uk sender: simon@pogner references: <51u63c$80c@netty.york.ac.uk> organization: At Home newsgroups: comp.lang.ada Date: 1996-09-23T00:00:00+00:00 List-Id: kst@thomsoft.com (Keith Thompson) writes: > In <520gjr$tf6@ktb2.ktb.net> obilynoh@ktb.net (Graffiti) writes: > > Although this post would be more appropriate in a linux newsgroup, I'll > > answer it anyways. Sig 11 indicates hardware trouble. > > Signal 11 is SIGSEGV, a segmentation violation. I've seen this a number > of times, but never due to hardware trouble. There are a number of > software problems that can cause a segmentation violation, including > dereferencing a null or garbage pointer. (On the other hand, I've never > used Linux; my experience has been on other Unix-like operating systems.) I had trouble with building the Linux kernel/gcc/gnat/emacs/things that required a lot of resources to compile. This sort of thing has been attributed to hardware (eg, doubtful memory) in the Linux groups. It went away for me after a recent kernel upgrade (2.0.17); but since I had the box apart in the same timescale and took the opportunity to jiggle the SIMMs I think this is a dubious datum :-) -- Simon Wright Work Email: simon.j.wright@gecm.com Ferranti Naval Systems Voice: +44(0)1705-701778 GEC-Marconi S3I Combat Systems Division FAX: +44(0)1705-701800