On Sat, Nov 22, 2003 at 02:57:51PM -0800, Ilya Zakharevich wrote: > The other segfault in newest lynx corresponds to > "unexpected network error" message on older lynxes, so > it should not be my fault. ;-) This is from "messages page" of older lynx: > > 24. Alert!: Unable to access document. > 23. Can't Access `http://www.cemi.rssi.ru/cyrtug/koi/news.htm' > 22. Alert!: Unexpected network read error; connection aborted. > 21. HTTP request sent; waiting for response. > 20. Sending HTTP request.
An update on this: I still can't connect to this site. However, restarting the most recent lynx "fixed" the segfault. Now I get the same messages from the new lynx as I do from an old one. So it looks like a memory corruption, so it *may* be related to a table code. Sigh... [This update still does not explain why some people/browsers can connect, some can't. Netscape and wget do not connect from my place either.] Yours, Ilya ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
