As I wasn't able do actually debug the crashes, I poked around a little in the
source and I think I found something.
I looked what happens when you set the -k option, and I found something that
*does not happen*, namely it doesn't look for the location of the cacert file
in the Windows version.
The Linux version has a default location for this file compiled in, but the
windows version has not. The internal variable for the name seems to stay
uninitialised in this case.

An indeed, it does not crash and works as expected, when you call it with a
cacert parameter, as in

curl --cacert anystring -k URL

The rest are various speculations now on my side: Maybe the variable with the
cacert file name is still used somewhere when the -k option is set. Maybe it
happened to be set to something harmless in the older Windows binaries and now
to something which causes a crash.

Regards, J.Roderburg
Received on 2005-01-14