[Top][All Lists]

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

Re: [Lynx-dev] --enable-nsl-fork doesn't always work ?

From: Frédéric L . W . Meunier
Subject: Re: [Lynx-dev] --enable-nsl-fork doesn't always work ?
Date: Sun, 22 Apr 2012 18:52:29 -0300
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Apr 22, 2012 at 05:40:47PM -0400, Thomas Dickey wrote:
> On Sun, Apr 22, 2012 at 05:36:13PM -0300, Frédéric L. W. Meunier wrote:
> > Here, it hangs at "Looking up", after ~10 
> > seconds returns "Alert!: Unable to connect to remote host." and I can 
> > get it back.
> > 
> > But I was wrong. I thought it worked on Slackware, but I compiled 
> > 2.8.8dev.12 on it and it does the same. 2.8.7rel.2 works fine.
> But "here" (Debian 5.0 with 2.8.2dev.12 or 2.8.7rel.1) both hang.
> The difference between rel.1/rel.2 is not related to this area.
> Comparing traces on your working/non-working versions might show
> something useful - if I trace it, I see this error:
>       HTParse:      result:`'
>       Looking up
>       HTGetAddrInfo: getaddrinfo(, 80): Name or service 
> not known
>       Unable to locate remote host
>       HTTP: Unable to connect to remote host for 
> `' (errno = 2).
>       Alert!: Unable to connect to remote host.
>       HTAccess:  status=-29999
>       HTAccess: `' has been accessed, No data 
> loaded.
>       stop_curses: done.
> fwiw, it also hangs from my desktop with firefox.

Sorry, I meant 2.8.7rel.1. Attached are the traces from Slackware 
-current. While 2.8.7rel.1 interrupts with 'z', with 2.8.8dev.12 (self 
compiled) it doesn't and I need to wait.

Attachment: Lynx.trace.bad
Description: Text document

Attachment: Lynx.trace.good
Description: Text document

reply via email to

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