RE: make check test failures with 2.4.1

["Steve Trotman" <strotman renlearn ca>]

Good guess!  It was reading the ipv6 hosts entry even though the ipv4
one is listed first in the /etc/hosts file, both named localhost.  I
commented out ::1 and ./dns now reads 127.0.0.1 as it should and all the
tests pass.  It is worth noting that that ipv6 entry in /etc/hosts DOES
NOT go away even if you switch off ipv6 in the network preferences pane
and/or use "ip6 -x" in the terminal window under os x tiger.  Leopard
did the same thing and has another bogus host entry called fe80::%lo0. 

-----Original Message-----
From: Dan Winship [mailto:danw gnome org] 
Sent: April-08-08 5:24 PM
To: Steve Trotman
Cc: libsoup-list gnome org
Subject: Re: make check test failures with 2.4.1

Steve Trotman wrote:
> I've attached the output from a ktrace of the debug enabled 
> continue-test

Blah. ktrace. Not quite as useful as strace output.

Anyway, it looks like (a) the server is successfully setting up the
listening socket, and (b) the client is repeatedly failing to be able to
connect to it. :-/

If you can gdb it, set a breakpoint on connect_watch() in soup-socket.c,
and see what the value of error is after the call to getsockopt.

Maybe its an IPv4 vs IPv6 thing? The SoupServer listens on the IPv4
interface, so if "localhost" resolved to an IPv6 address, that would
cause problems. If you do "./dns localhost" (in the tests directory),
does it return "127.0.0.1" or "::1"?

-- Dan