zeromq / libzmq / 2333

75%

Pull #2090

travis-ci

<a href="https://github.com/zeromq/libzmq/commit/<a class=hub.com/zeromq/libzmq/commit/f59071fb400f2739cfcd9258c66893086edbda54">f59071fb4<a href="https://github.com/zeromq/libzmq/commit/f59071fb400f2739cfcd9258c66893086edbda54">&quot;&gt;[gssapi] memory allocation mismatch on windows

The gssapi has some helper functions gssalloc_malloc()/gssalloc_free()
which on windows doesn&amp;#39;t call malloc()/free(). Instead these are
wrappers around HeapAlloc() and HeapFree(). To complicate matters
gssapi doesn&amp;#39;t export these helper functions, so you&amp;#39;re left using
the allocation method of your choice.

See Here:
https://github.com/krb5/krb5/blob/</a><a class="double-link" href="https://github.com/zeromq/libzmq/commit/<a class="double-link" href="https://github.com/zeromq/libzmq/commit/89683d1f135765e91041f3a239af865b11aaf86b">89683d1f1</a>">89683d1f1</a><a href="https://github.com/zeromq/libzmq/commit/f59071fb400f2739cfcd9258c66893086edbda54">/src/lib/gssapi/generic/gssapi_alloc.h

The zmq gssapi implementation is calling malloc and then calling
gss_release_buffer() to free the memory. gss_release_buffer uses
gssalloc_free() to free this buffer which on windows calls HeapFree()
instead of free(). This causes an access violation on windows.

8231 of 10937 relevant lines covered (75.26%)

22878.97 hits per line