curl-library
Re: BUG: NULL pointer dereference in Curl_ssl_getsessionid.
Date: Sun, 28 Apr 2013 16:08:51 +0200
Hi Daniel,
2013/4/20 Daniel Stenberg <daniel_at_haxx.se>:
> Any chance one of you can get some debug info there so that we get to know
> on what exact source line it crashes and some variable/argument contents?
Here are the details you asked for:
(gdb) run
Starting program: d:\OS\curl\src\curl.exe -g https://google.com/
[New Thread 4324.0x1670]
[New Thread 4324.0x1624]
[New Thread 4324.0x1784]
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="https://www.google.com/">here</A>.
</BODY></HTML>
[New Thread 4324.0x157c]
[New Thread 4324.0x1bdc]
Program received signal SIGSEGV, Segmentation fault.
0x0041c136 in Curl_ssl_getsessionid (conn=0x845b88, ssl_sessionid=0x28f868,
idsize=0x0) at sslgen.c:258
258 if(!check->sessionid)
(gdb) bt
#0 0x0041c136 in Curl_ssl_getsessionid (conn=0x845b88,
ssl_sessionid=0x28f868, idsize=0x0) at sslgen.c:258
#1 0x00430712 in Curl_schannel_shutdown (conn=0x845b88, sockindex=0)
at curl_schannel.c:1146
#2 0x0041c6af in Curl_ssl_shutdown (conn=0x845b88, sockindex=0)
at sslgen.c:426
#3 0x00430443 in Curl_schannel_close (conn=0x845b88, sockindex=0)
at curl_schannel.c:1056
#4 0x0041c695 in Curl_ssl_close (conn=0x845b88, sockindex=0) at sslgen.c:421
#5 0x00421356 in Curl_disconnect (conn=0x845b88, dead_connection=false)
at url.c:2567
#6 0x00429217 in close_all_connections (multi=0x82d7b0) at multi.c:1770
#7 0x0042926a in curl_multi_cleanup (multi_handle=0x82d7b0) at multi.c:1786
#8 0x0041d89c in Curl_close (data=0x822ff0) at url.c:392
#9 0x00416eda in curl_easy_cleanup (curl=0x822ff0) at easy.c:507
#10 0x0040ecb1 in operate (config=0x28fd08, argc=3, argv=0x822fc0)
at tool_operate.c:1744
#11 0x00409930 in main (argc=3, argv=0x822fc0) at tool_main.c:100
> I don't think this has a lot to do with the multi interface and how that
> works, I bet my money on the schannel code, the sessionid cache and how they
> interoperate.
Yes, it's probably the fact that the schannel code uses
Curl_ssl_getsessionid within the Curl_ssl_shutdown function which may
not be supported by the ssl abstraction layer.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-04-28