OK - now that I've got gdb working...

  $ curl.exe "http://testweb/thr/" --http1.0 --trace /tmp/trace.log

yields a SEG FAULT at memdebug.c:158, in the function curl_dofree. Here's a bit of the stack:

 #0 _libkernel32_a_iname ()
 #1 ?? ()
 #2 _libkernel32_a_iname ()
 #3 curl_dofree (ptr=0x100de7d8, line=1113, source="url.c") at memdebug.c:158
 #4 Curl_disconnect (conn=0x100ddc98) at url.c:1113
 #5 ConnectionKillOne (data=0x100c9500) at url.c:1313
 #6 Curl_close (data=0x100c9500) at url.c:175
 #7 curl_easy_cleanup (curl=0x100c9500) at easy.c:254
 #8 operate (config=0x22fc50, argc=3, argv=0x100c2108) at main.c:2910
 #9 main (argc=3, argv=0x100c2108) at main.c:2927

*ptr is 0x100de7d8. *mem is 0x100de7d0. Here's a bit of the memory:

 0x100de7d0: 0x0000004c 0x00000244 0x13131313 0x13131313 ...

The segfault happens while calling (free)(mem).

That's all I know or am capable of digging up. Anyone capable of taking this further?

--Kevin

-----Original Message-----
From: Roth, Kevin P.
Sent: Tuesday, September 10, 2002 5:16 PM

Yes - this happens at a cygwin prompt also. Win2k Professional Service Pack 2 for what it's worth (haven't tried yet on other service pack levels or another windows os).

Due to some problems using GDB (specifically something barfs when calling out to "Non-Debugging functions" such as gethostbyname(), socket(), etc...) I'm unable to run this through gdb at present.

Could our win32 expert (Joern, where are you?) try running this to see whether he sees the same issue? If so, does he have a debugger?

--Kevin

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Thursday, September 05, 2002 10:47 AM

On Thu, 5 Sep 2002, Roth, Kevin P. wrote:
> One was a combination of --http1.0 with --trace:
>
> $ curl.exe "http://testweb/thr/" --http1.0 --trace trace.log
> < response snipped >
>
> 5 [main] curl 2560 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
> 1143 [main] curl 2560 open_stackdumpfile: Dumping stack trace

And this happens repeatedly? Any way you can check where in the code this
barfs? I've tried with very similar command lines on Linux and Solaris
without seeing anything weird happen.

> Another was a difference between using a proxy or not. This works (except
> for the .zip file problem...):

Same here. I got a report from another Windows user who failed to use
7.10-pre2 over a proxy to fetch FTP files, but I just can't repeat these
problems on my systems.

If you run this at a the cygwin prompt, do they happen then too? Can you run
gdb on the binary then to debug it?

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2002-09-12