[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev 2.8.4dev.2 on OS/390 2.8
From: |
Phil Sidler |
Subject: |
Re: lynx-dev 2.8.4dev.2 on OS/390 2.8 |
Date: |
Tue, 23 May 2000 15:32:38 -0700 |
Trace doesn't show much ("Entering mainloop, startfile=...") but sometimes I
get an 0C4 CEE dump. That's at least something I can deal with. Seems to
be failing in getfile().
But, I rebuilt lynx with --enable-debug to get better info in the dump and
then it didn't fail, perhaps because this turns off optimization. I hate
these kinds of problems. So, it's maybe a compiler bug. I'll let you know
what I find out.
(No, I don't usually use lynx with xterm. Mainly I use telnet under
Windoze.)
----- Original Message -----
From: <address@hidden>
To: <address@hidden>
Sent: Tuesday, May 23, 2000 2:08 PM
Subject: Re: lynx-dev 2.8.4dev.2 on OS/390 2.8
In a recent note, Phil Sidler said:
> Date: Tue, 23 May 2000 13:51:27 -0700
>
> failed...
>
> A Fatal error has occurred in Lynx Ver. 2.8.4dev.2
>
> Lynx now exiting with signal: 11
>
> CEE5207E The signal SIGABRT was received.
> [1] + Done(131) ./lynx
> 83886392 Abort ./lynx
>
>
> How do I tell what the fatal error was? I doesn't seem to matter what the
> URL is, they all fail.
>
First, try running "lynx -trace" and see if there's anything meaningful
in ~/Lynx.trace.
You appear to be running on OS/390. I still haven't tried any
lynx 2.8.4* on OS/390, so I can't confirm or contrast your experience.
BTW, are you using Lynx with xterm XFree86 on OS/390? Just curious
what your experiences are?
-- gil
--
StorageTek
INFORMATION made POWERFUL
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden