lynx-dev
[Top][All Lists]
Advanced

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

Re: LYNX-DEV Lynx / News bug?


From: Allan Foster
Subject: Re: LYNX-DEV Lynx / News bug?
Date: Thu, 13 Nov 1997 10:37:50 -0600

Hello

We were having the problem with the fatal error and ACCVIO when trying to
access NEWS from LYNX after we upgraded to Alpha OpenVMS 7.1 from 6.2. We 
were using the current version from Fotes site LYNX2-7-1f.

We built lynx using the DEBUG option and noticed that NEWS worked fine so 
looking at build.com cc_opts = "/debug/noopt" and without debug cc_opts = "".

So we changed build.com so it would compile with /nooptimize on the normal
build and it built fine and news works again.

Here is the section of build.com and the line we added..

$ link_opts = ""
$!
$ if p2 .nes. ""
$   then
$      debug_arg = "DEBUG"
$      cc_opts = cc_opts + "/DEBUG/NOOPT"
$      link_opts = link_opts + "/DEBUG"
$   else
$      cc_opts = cc_opts + "/NOOPT"     ! Added to compile with /nooptimize 
$      debug_arg = ""
$ endif

I just thought I would post this in case anyone encounters the same problem
down the road. I dont know why it works this way but as they say "if it ain't
broke..." . I will include the original error we were getting below...

--------------------------------------------------------------------------------
Allan J. Foster                         | "It might be the easy way...but it   
Computing and Information Resources     |  wouldn't be the Cowboy Way."
The University of Tulsa                 |                   Ranger Doug    
918.631.2342  address@hidden |                   Riders in the Sky
--------------------------------------------------------------------------------


%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000007FFA
1E58, PC=FFFFFFFF800C53A8, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 0000000000000005
                        Name   = 000000000000000C
                                 7FFA1E5800010000
                                 800C53A87FFA1E58
                                 0000001B800C53A8
                                 000000050000001B

    Register dump:
    R0  = 0000000000158001  R1  = 0000000000000000  R2  = 0000000000000003
    R3  = 0000000000000001  R4  = 0000000000000001  R5  = 0000000000000000
    R6  = 0000000000000000  R7  = 000000007AF5EA40  R8  = 0000000000452038
    R9  = 0000000000000000  R10 = 0000000000000000  R11 = 0000000000000000
    R12 = 0000000000000000  R13 = FFFFFFFF80C4B170  R14 = FFFFFFFF80F9E6C0
    R15 = 000000007AF5E7A4  R16 = 00000000003E0040  R17 = 00000000003E0030
    R18 = 0000000000452030  R19 = FFFFFFFF80C05000  R20 = 0000000000000000
    R21 = 0000000000000000  R22 = 0000000000158001  R23 = 0000000000158001
    R24 = FFFFFFFFFFFFFFFF  R25 = 0000000000000003  R26 = FFFFFFFF800C53A8
    R27 = 000000007B1EEC80  R28 = 0000000000000000  R29 = 000000007FFA1E40
    SP  = 000000007AF5E0F0  PC  = FFFFFFFF800C53A8  PS  = 300000000000001B

A Fatal error has occured in Lynx Ver. 2.7.1f

Please notify your system administrator to confirm a bug, and if
confirmed, to notify the lynx-dev list.  Bug reports should have concise
descriptions of the command and/or URL which causes the problem, the
operating system name with version number, the TCPIP implementation, the
TRACEBACK if it can be captured, and any other relevant information.
 
;
; 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]