On Mon, 21 Sep 2009, Ganesh Ragavan wrote: Top-posting is not appreciated on this list. Please stop that.
I also checked the SSL_shutdown() input value, its a pointer and it is not null.
Of course it is. That's what SSL_shutdown() should get as input. You could set a break-point there with your debugger and investigate the data at the moment it crashes. Or you can run the test case with valgrind or similar to see if you can catch some other kind of bad memory access or so.
I tried using https://ipv4_address:443/.. instead of https://ipv6_address:443/... but it still crashes; difference being it crashes at 3001 th iteration instead of 1001th iteration for ipv6.
Is it exactly those numbers every time? That feels like some kind of fixed boundaries or limited-sized arrays or something that get hit. I don't mean within libcurl then as it doesn't have any such.
So my advice is still to break-point at the point it crashes. The fact that it repeats easily should also make debugging this fairly easy.
Or work on making an example program that repeats this behavior for us. -- / daniel.haxx.se
