Attachment 12098 Details for Bug 11914 – valgrind ntlm_auth

valgrind ntlm_auth

valgrind.ntlm_auth.18593 (text/plain), 4.23 KB, created by Konstantin Belov on 2016-05-11 11:06:56 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Konstantin Belov

Created: 2016-05-11 11:06:56 UTC

Size: 4.23 KB

patch

obsolete

>==18593== Memcheck, a memory error detector
>==18593== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
>==18593== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
>==18593== Command: /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
>==18593== Parent PID: 18484
>==18593== 
>==18593== Invalid read of size 8
>==18593==    at 0xA81F9B0: security_token_is_sid (in /usr/lib/x86_64-linux-gnu/samba/libsamba-security.so.0)
>==18593==    by 0xA821908: security_session_user_level (in /usr/lib/x86_64-linux-gnu/samba/libsamba-security.so.0)
>==18593==    by 0x54936BA: gensec_ntlmssp_server_auth (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x548EE92: gensec_ntlmssp_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499A99: gensec_update_ev (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499AD6: gensec_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x10FBBD: manage_gensec_request.isra.5 (in /usr/bin/ntlm_auth)
>==18593==    by 0x10D3CE: manage_squid_request (in /usr/bin/ntlm_auth)
>==18593==    by 0x10CDAA: main (in /usr/bin/ntlm_auth)
>==18593==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
>==18593== 
>==18593== 
>==18593== Process terminating with default action of signal 11 (SIGSEGV)
>==18593==  Access not within mapped region at address 0x8
>==18593==    at 0xA81F9B0: security_token_is_sid (in /usr/lib/x86_64-linux-gnu/samba/libsamba-security.so.0)
>==18593==    by 0xA821908: security_session_user_level (in /usr/lib/x86_64-linux-gnu/samba/libsamba-security.so.0)
>==18593==    by 0x54936BA: gensec_ntlmssp_server_auth (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x548EE92: gensec_ntlmssp_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499A99: gensec_update_ev (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499AD6: gensec_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x10FBBD: manage_gensec_request.isra.5 (in /usr/bin/ntlm_auth)
>==18593==    by 0x10D3CE: manage_squid_request (in /usr/bin/ntlm_auth)
>==18593==    by 0x10CDAA: main (in /usr/bin/ntlm_auth)
>==18593==  If you believe this happened as a result of a stack
>==18593==  overflow in your program's main thread (unlikely but
>==18593==  possible), you can try to increase the size of the
>==18593==  main thread stack using the --main-stacksize= flag.
>==18593==  The main thread stack size used in this run was 8388608.
>==18593== Invalid free() / delete / delete[] / realloc()
>==18593==    at 0x4C2BDEC: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
>==18593==    by 0x7B075AB: __libc_freeres (in /lib/x86_64-linux-gnu/libc-2.19.so)
>==18593==    by 0x4A256BC: _vgnU_freeres (in /usr/lib/valgrind/vgpreload_core-amd64-linux.so)
>==18593==    by 0xA821908: security_session_user_level (in /usr/lib/x86_64-linux-gnu/samba/libsamba-security.so.0)
>==18593==    by 0x54936BA: gensec_ntlmssp_server_auth (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x548EE92: gensec_ntlmssp_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499A99: gensec_update_ev (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x5499AD6: gensec_update (in /usr/lib/x86_64-linux-gnu/libgensec.so.0.0.1)
>==18593==    by 0x10FBBD: manage_gensec_request.isra.5 (in /usr/bin/ntlm_auth)
>==18593==    by 0x10D3CE: manage_squid_request (in /usr/bin/ntlm_auth)
>==18593==    by 0x10CDAA: main (in /usr/bin/ntlm_auth)
>==18593==  Address 0x7d603c0 is 0 bytes inside data symbol "noai6ai_cached"
>==18593== 
>==18593== 
>==18593== HEAP SUMMARY:
>==18593==     in use at exit: 70,308 bytes in 187 blocks
>==18593==   total heap usage: 531 allocs, 345 frees, 183,129 bytes allocated
>==18593== 
>==18593== LEAK SUMMARY:
>==18593==    definitely lost: 1,101 bytes in 5 blocks
>==18593==    indirectly lost: 264 bytes in 7 blocks
>==18593==      possibly lost: 67,232 bytes in 168 blocks
>==18593==    still reachable: 1,711 bytes in 7 blocks
>==18593==         suppressed: 0 bytes in 0 blocks
>==18593== Rerun with --leak-check=full to see details of leaked memory
>==18593== 
>==18593== For counts of detected and suppressed errors, rerun with: -v
>==18593== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

Actions: View

Attachments on bug 11914: 12097 | 12098 | 12100 | 12114 | 12115 | 12116