lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Fatal error Lynx Ver. 2.6


From: Foteos Macrides
Subject: Re: LYNX-DEV Fatal error Lynx Ver. 2.6
Date: Tue, 29 Oct 1996 13:09:39 -0500 (EST)

Foteos Macrides <address@hidden> wrote:
>address@hidden (Drazen Kacar) wrote:
>>Michael Lerperger wrote:
>>> 
>>> Exiting via interrupt: 0
>>> Unaligned access pid=3284 <lynx> va=74736f686c61636f pc=120015cd0 
>>> ra=120015cf8
>>> type=stq
>>  ^^^^^^^^
>>> 
>>> OS: OSF1v4.0
>>> COMPILER: default entry for "osf" in the top level Makefile:
>>
>>I've never worked on OSF, but this stq looks like "store quadruple" 
>>instruction.
>>On most RISCs instructions of this type will try to store 8 byte entity to
>>memory, but the alignment is important. The address must be on 8 byte 
>>boundary.
>>If this is the reason, than it's a big bug in Lynx.
>
>       I looked at stdin.h on an OSF/AXP, and it's defining NULL as 0L.
>I wonder if the 0 arguments without pointer type casts still here and
>there in the LYfoo and libwww modules have anything to do with it.

        Try adding -misalign to the OSF's cc command.  If Drazen's guess
is right, that should get you past the problem, for now (at least, if
what the OSF's man says for cc is true 8-).

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]