On Thu, 9 Dec 2004, Daniel Stenberg wrote:

> Try running test case 1 with more verbose options:
>
> ./runtests.pl -d -v -p 1
>
> ... it might reveal the specific point where it stops better.

And so it does:

test 001...CMD; ../src/curl -o log/verifiedserver
http://127.0.0.1:8990/verifiedserver 2>/dev/null
RUN: curl command returned 7
CMD: perl -I. ./httpserver.pl -v 8990 &

So, sws is getting started, and runtests.pl never gets past here:

# verify that our server is up and running:
my $data=`$CURL --silent $HOSTIP:$HTTPPORT/verifiedserver 2>/dev/null`;

When I try running sws alone, and then running curl myself from the
command line, curl doesn't return. I invoke it like this:

$ ../src/curl http://127.0.0.1:8990/verifiedserver --trace-ascii foo.txt

and foo.txt contains

== Info: About to connect() to 127.0.0.1 port 8990
== Info: Trying 127.0.0.1... == Info: connected
== Info: Connected to 127.0.0.1 (127.0.0.1) port 8990
=> Send header, 176 bytes (0xb0)
0000: GET /verifiedserver HTTP/1.1
001e: User-Agent: curl/7.12.3-CVS (i686-pc-cygwin) libcurl/7.12.3-CVS
005e: OpenSSL/0.9.7d zlib/1.2.1
0079: Host: 127.0.0.1:8990
008f: Pragma: no-cache
00a1: Accept: */*
00ae:
<= Recv header, 17 bytes (0x11)
0000: HTTP/1.1 200 OK
<= Recv data, 16 bytes (0x10)
0000: WE ROOLZ: 5772

BTW, when I get http://www.google.com, curl returns fine. I also tried
this with my win32 build of curl from yesterday's CVS and an older
version and both of them return fine both from google and the test
server. They fail in the testsuite because (if I remember right)
runtest can't set environment variables that win32 programs can see.
I'm not worried about this right now.

I guess something ain't right with my cygwin build or my cygwin
installation.

-DB
Received on 2004-12-10