Attachment 18305 Details for Bug 15652 – valgrind output

valgrind output

valgrind.txt (text/plain), 3.80 KB, created by Marvin Adams on 2024-05-29 12:51:51 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marvin Adams

Created: 2024-05-29 12:51:51 UTC

Size: 3.80 KB

patch

obsolete

>==8975== Memcheck, a memory error detector
>==8975== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
>==8975== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info
>==8975== Command: /usr/sbin/named -u named
>==8975== 
>==8976== Thread 2:
>==8976== Syscall param socketcall.bind(my_addr.nl_pid) points to uninitialised byte(s)
>==8976==    at 0x403B083: __syscall6 (syscall_arch.h:59)
>==8976==    by 0x403B083: __alt_socketcall (syscall.h:65)
>==8976==    by 0x403B083: bind (bind.c:6)
>==8976==    by 0x48E9BD8: route_socket (udp.c:242)
>==8976==    by 0x48E9BD8: isc_nm_routeconnect (udp.c:370)
>==8976==    by 0x4B0EBED: ns_interfacemgr_create (interfacemgr.c:352)
>==8976==    by 0x142D76: run_server (server.c:10043)
>==8976==    by 0x49049CE: task_run (task.c:815)
>==8976==    by 0x49049CE: isc_task_run (task.c:896)
>==8976==    by 0x48D6259: isc__nm_async_task (netmgr.c:860)
>==8976==    by 0x48DC30A: process_netievent (netmgr.c:942)
>==8976==    by 0x48DCB67: process_queue (netmgr.c:1035)
>==8976==    by 0x48DD356: process_all_queues (netmgr.c:773)
>==8976==    by 0x48DD356: async_cb (netmgr.c:802)
>==8976==    by 0x4FF8DAA: ??? (in /usr/lib/libuv.so.1.0.0)
>==8976==    by 0x500D052: ??? (in /usr/lib/libuv.so.1.0.0)
>==8976==    by 0x4FF9AD2: uv_run (in /usr/lib/libuv.so.1.0.0)
>==8976==  Address 0x58a7530 is on thread 2's stack
>==8976==  in frame #1, created by isc_nm_routeconnect (udp.c:346)
>==8976==  Uninitialised value was created by a stack allocation
>==8976==    at 0x48E9AB0: isc_nm_routeconnect (udp.c:346)
>==8976== 
>==8976== Invalid read of size 8
>==8976==    at 0x7180470: heim_get_debug_dest (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x7180FCB: heim_debug (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x718342C: heim_plugin_register (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x66E8418: smb_krb5_init_context_basic (in /usr/lib/samba/libauthkrb5-samba4.so)
>==8976==    by 0x66E8620: smb_krb5_init_context (in /usr/lib/samba/libauthkrb5-samba4.so)
>==8976==    by 0x64BC50A: dlz_create (in /usr/lib/samba/bind9/dlz_bind9_18.so)
>==8976==    by 0x123DB7: dlopen_dlz_create (dlz_dlopen_driver.c:313)
>==8976==    by 0x4A2DD81: dns_sdlzcreate (sdlz.c:1603)
>==8976==    by 0x4980897: dns_dlzcreate (dlz.c:212)
>==8976==    by 0x133F36: configure_view (server.c:4303)
>==8976==    by 0x1419A4: load_configuration (server.c:9343)
>==8976==    by 0x142EEB: run_server (server.c:10080)
>==8976==  Address 0x970ea734 is not stack'd, malloc'd or (recently) free'd
>==8976== 
>==8976== 
>==8976== Process terminating with default action of signal 11 (SIGSEGV): dumping core
>==8976==  Access not within mapped region at address 0x970EA734
>==8976==    at 0x7180470: heim_get_debug_dest (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x7180FCB: heim_debug (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x718342C: heim_plugin_register (in /usr/lib/samba/libheimbase-samba4.so)
>==8976==    by 0x66E8418: smb_krb5_init_context_basic (in /usr/lib/samba/libauthkrb5-samba4.so)
>==8976==    by 0x66E8620: smb_krb5_init_context (in /usr/lib/samba/libauthkrb5-samba4.so)
>==8976==    by 0x64BC50A: dlz_create (in /usr/lib/samba/bind9/dlz_bind9_18.so)
>==8976==    by 0x123DB7: dlopen_dlz_create (dlz_dlopen_driver.c:313)
>==8976==    by 0x4A2DD81: dns_sdlzcreate (sdlz.c:1603)
>==8976==    by 0x4980897: dns_dlzcreate (dlz.c:212)
>==8976==    by 0x133F36: configure_view (server.c:4303)
>==8976==    by 0x1419A4: load_configuration (server.c:9343)
>==8976==    by 0x142EEB: run_server (server.c:10080)
>==8976==  If you believe this happened as a result of a stack
>==8976==  overflow in your program's main thread (unlikely but
>==8976==  possible), you can try to increase the size of the
>==8976==  main thread stack using the --main-stacksize= flag.
>==8976==  The main thread stack size used in this run was 8388608.
>==8976==

Actions: View

Attachments on bug 15652: 18304 | 18305