Summary: Segmentation Violation

From: Ron Madurski (ron@drd.com)
Date: Wed Oct 09 1991 - 18:59:58 CDT


Here are some of the replies that I have received and the names of other
people that sent basically the same info.

Thanks to all, and I apologize for sending the traceback.

From: macphed@dvinci.usask.ca (Ian MacPhedran)

>> I had always thought that Segmention Violations were memory problems but
>> I'm not sure.
>>
>> Do the Signal and code numbers have any significant meaning and if so
>> where do I find this meaning?

man 2 sigvec

>> Thanks for any help.
>>
>> *** Segmentation Violation = signal 11 code 3

signal 11 = SIGSEGV (signals segmentation violation - sigvec(2) and
                    /usr/include/sys/signal.h - included in signal.h)
code 3 = FC_NOMAP ( no mapping at the fault address -
                    /usr/include/vm/faultcode.h - included in sys/signal.h)

I.e. you are addressing something outside memory.

From: phil@pex.eecs.nwu.edu (William LeFebvre)

A segmentatino violation is generated when an attempt is made to access
a virtual memory address which has not been allocated (that is, there is
no physical memory and no backing store associated with the address).
***or tried to write to something which is read-only.
(*** added from another reply)

> Do the Signal and code numbers have any significant meaning and if so
> where do I find this meaning?

Yes. man signal, man sigvec, and the include file
/usr/include/vm/faultcode.h

> *** Segmentation Violation = signal 11 code 3

signal 11 is a SIGSEGV, or a segmentation violation. But you already
knew this from the rest of the error message. The codes are described in
/usr/include/vm/faultcode.h. A code 3 is:

#define FC_NOMAP 0x3 /* no mapping at the fault address */

> Cant open file for traceback
> Expect output on terminal
> Note: Line numbers for system and library calls may be incorrect
> Begin traceback...
> Called from 0x925dd4 , at 0xf7ffea08, args=0xb 0xffffffff 0x6 0xb3e3cc
..

Numerical tracebacks are totally useless. Please see the Policy
statement that was posted on this list earlier this month.
Specifically:

9: When including a traceback from a system panic, make sure that it is
    a SYMBOLIC traceback. Numeric tracebacks (the ones included as part
    of the panic message) are totally useless. Read chapter 22 of the
    SunOS 4.1 system administration manual to learn how to produce a
    symbolic traceback.

 "Matt Crawford" <matt@oddjob.uchicago.edu>
 stern@sunne.East.Sun.COM (Hal Stern - Consultant)

 Thanks again.

-- 
ron@DRD.Com         
uunet!apctrc!drd!ron   



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:18 CDT