[libmicrohttpd] Recursive lock in GIT

2017-05-21 Thread Markus Doppelbauer
Hello, I have updated "0.9.53" to GIT - maybe a week ago. There is a recursive lock to "daemon->cleanup_connection_mutex" __owner=6065 holds the lock - but tries to lock again in "connection.c:2837" The callstack:     "resume_suspended_connections()" at daemon.c:2908     "MHD_conne

Re: [libmicrohttpd] Recursive lock in GIT

2017-05-21 Thread Evgeny Grin
Hi Markus, Thanks for report! Could you provide more information? Why connection was closed right after resume? -- Wishes, Evgeny On 21.05.2017 13:52, Markus Doppelbauer wrote: > Hello, > > I have updated "0.9.53" to GIT - maybe a week ago. > There is a recursive lock to "daemon->cleanup_conne

Re: [libmicrohttpd] Recursive lock in GIT

2017-05-21 Thread Markus Doppelbauer
Dear Evgeny, Maybe because the request-headers contain "Connection: close"? This is what I could determine with `gdb`: (gdb) frame 4 (gdb) p *connection->headers_received GET / HTTP/1.1 Host: server.name Connection: close Content-Length: 4 Accept-Encoding: gzip Accept: */* Content-Type: application

Re: [libmicrohttpd] Recursive lock in GIT

2017-05-21 Thread Evgeny Grin
IE 4.01 on Win95? Cool. :) Should be fixed in master. Could you check it? -- Best Wishes, Evgeny Grin On 21.05.2017 16:30, Markus Doppelbauer wrote: > Dear Evgeny, > > Maybe because the request-headers contain "Connection: close"? > This is what I could determine with `gdb`: > > (gdb) frame 4