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


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