Hi Volker; I have run with "gdb" as : #gdb --args net ads join -S CINVW067 -U administrateur%laposte+1 At the prompt : "run," when it crashes "bt" and see the backtrace : (gdb) run Starting program: /usr/bin/net ads join -S CINVW067 -U administrateur%laposte+1 Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2 Failed to read a valid object file image from memory. Missing separate debuginfo for /lib64/libresolv.so.2 Missing separate debuginfo for /lib64/libnsl.so.1 Missing separate debuginfo for /lib64/libdl.so.2 Missing separate debuginfo for /lib64/librt.so.1 Missing separate debuginfo for /usr/lib64/libpopt.so.0 Missing separate debuginfo for /usr/lib64/libgssapi_krb5.so.2 Missing separate debuginfo for /usr/lib64/libkrb5.so.3 Missing separate debuginfo for /usr/lib64/libk5crypto.so.3 Missing separate debuginfo for /lib64/libcom_err.so.2 Missing separate debuginfo for /lib64/libuuid.so.1 Missing separate debuginfo for /usr/lib64/libldap-2.3.so.0 Missing separate debuginfo for /usr/lib64/liblber-2.3.so.0 Missing separate debuginfo for /lib64/libnscd.so.1 Missing separate debuginfo for /lib64/libreadline.so.5 Missing separate debuginfo for /usr/lib64/libwbclient.so.0 Missing separate debuginfo for /lib64/libz.so.1 Missing separate debuginfo for /lib64/libc.so.6 Missing separate debuginfo for /lib64/libpthread.so.0 [Thread debugging using libthread_db enabled] Missing separate debuginfo for /usr/lib64/libkrb5support.so.0 Missing separate debuginfo for /usr/lib64/libsasl2.so.2 Missing separate debuginfo for /usr/lib64/libssl.so.0.9.8 Missing separate debuginfo for /usr/lib64/libcrypto.so.0.9.8 Missing separate debuginfo for /lib64/libncurses.so.5 Missing separate debuginfo for /usr/lib64/gconv/UTF-16.so Missing separate debuginfo for /usr/lib64/gconv/IBM850.so Program received signal SIGSEGV, Segmentation fault. 0x00002aaaab25a4dd in krb5_ktfile_get_next () from /usr/lib64/libkrb5.so.3 (gdb) bt #0 0x00002aaaab25a4dd in krb5_ktfile_get_next () from /usr/lib64/libkrb5.so.3 #1 0x0000555555a3acba in smb_krb5_kt_add_entry_ext () from /usr/bin/net #2 0x0000555555a3afa3 in smb_krb5_kt_add_entry () from /usr/bin/net #3 0x0000555555a3b63f in ads_keytab_add_entry () from /usr/bin/net #4 0x0000555555a3b85b in ads_keytab_create_default () from /usr/bin/net #5 0x0000555555a777db in libnet_Join () from /usr/bin/net #6 0x0000555555631c3b in net_ads_join () from /usr/bin/net #7 0x000055555565fa93 in net_run_function () from /usr/bin/net #8 0x0000555555630360 in net_ads () from /usr/bin/net #9 0x000055555565fa93 in net_run_function () from /usr/bin/net #10 0x000055555562f461 in main () from /usr/bin/net
Regards --- En date de : Mar 22.11.11, djamel boussebha <[email protected]> a écrit : De: djamel boussebha <[email protected]> Objet: Re: [Samba] ADS Problem : segmentation fault À: [email protected] Cc: [email protected] Date: Mardi 22 novembre 2011, 11h45 See the results of the command : # valgrind --tool=memcheck net ads join -S CINVW067 -U administrateur%laposte+1 ==9483== Memcheck, a memory error detector ==9483== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==9483== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==9483== Command: net ads join -S CINVW067 -U administrateur%laposte+1 ==9483== ==9483== Syscall param socketcall.sendto(msg) points to uninitialised byte(s) ==9483== at 0x5D98B63: __sendto_nocancel (in /lib64/libc-2.4.so) ==9483== by 0x5DB4333: __netlink_request (in /lib64/libc-2.4.so) ==9483== by 0x5DB45EC: getifaddrs (in /lib64/libc-2.4.so) ==9483== by 0x33ABC9: get_interfaces (in /usr/bin/net) ==9483== by 0x348FEF: load_interfaces (in /usr/bin/net) ==9483== by 0x1E3415: main (in /usr/bin/net) ==9483== Address 0x7feffeae1 is on thread 1's stack ==9483== ==9483== Syscall param socketcall.sendto(msg) points to uninitialised byte(s) ==9483== at 0x5D98B63: __sendto_nocancel (in /lib64/libc-2.4.so) ==9483== by 0x5DB4333: __netlink_request (in /lib64/libc-2.4.so) ==9483== by 0x5DB4609: getifaddrs (in /lib64/libc-2.4.so) ==9483== by 0x33ABC9: get_interfaces (in /usr/bin/net) ==9483== by 0x348FEF: load_interfaces (in /usr/bin/net) ==9483== by 0x1E3415: main (in /usr/bin/net) ==9483== Address 0x7feffeae1 is on thread 1's stack ==9483== ==9483== Invalid read of size 8 ==9483== at 0x51B74DD: krb5_ktfile_get_next (in /usr/lib64/libkrb5.so.3.2) ==9483== by 0x5EECB9: smb_krb5_kt_add_entry_ext (in /usr/bin/net) ==9483== by 0x5EEFA2: smb_krb5_kt_add_entry (in /usr/bin/net) ==9483== by 0x5EF63E: ads_keytab_add_entry (in /usr/bin/net) ==9483== by 0x5EF85A: ads_keytab_create_default (in /usr/bin/net) ==9483== by 0x62B7DA: libnet_Join (in /usr/bin/net) ==9483== by 0x1E5C3A: net_ads_join (in /usr/bin/net) ==9483== by 0x213A92: net_run_function (in /usr/bin/net) ==9483== by 0x1E435F: net_ads (in /usr/bin/net) ==9483== by 0x213A92: net_run_function (in /usr/bin/net) ==9483== by 0x1E3460: main (in /usr/bin/net) ==9483== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==9483== ==9483== ==9483== Process terminating with default action of signal 11 (SIGSEGV) ==9483== Access not within mapped region at address 0x0 ==9483== at 0x51B74DD: krb5_ktfile_get_next (in /usr/lib64/libkrb5.so.3.2) ==9483== by 0x5EECB9: smb_krb5_kt_add_entry_ext (in /usr/bin/net) ==9483== by 0x5EEFA2: smb_krb5_kt_add_entry (in /usr/bin/net) ==9483== by 0x5EF63E: ads_keytab_add_entry (in /usr/bin/net) ==9483== by 0x5EF85A: ads_keytab_create_default (in /usr/bin/net) ==9483== by 0x62B7DA: libnet_Join (in /usr/bin/net) ==9483== by 0x1E5C3A: net_ads_join (in /usr/bin/net) ==9483== by 0x213A92: net_run_function (in /usr/bin/net) ==9483== by 0x1E435F: net_ads (in /usr/bin/net) ==9483== by 0x213A92: net_run_function (in /usr/bin/net) ==9483== by 0x1E3460: main (in /usr/bin/net) ==9483== If you believe this happened as a result of a stack ==9483== overflow in your program's main thread (unlikely but ==9483== possible), you can try to increase the size of the ==9483== main thread stack using the --main-stacksize= flag. ==9483== The main thread stack size used in this run was 8388608. ==9483== ==9483== HEAP SUMMARY: ==9483== in use at exit: 472,560 bytes in 625 blocks ==9483== total heap usage: 30,060 allocs, 29,435 frees, 2,791,523 bytes allocated ==9483== ==9483== LEAK SUMMARY: ==9483== definitely lost: 25 bytes in 1 blocks ==9483== indirectly lost: 0 bytes in 0 blocks ==9483== possibly lost: 14,254 bytes in 138 blocks ==9483== still reachable: 458,281 bytes in 486 blocks ==9483== suppressed: 0 bytes in 0 blocks ==9483== Rerun with --leak-check=full to see details of leaked memory ==9483== ==9483== For counts of detected and suppressed errors, rerun with: -v ==9483== Use --track-origins=yes to see where uninitialised values come from ==9483== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 3 from 3) Segmentation fault A idea on this crash ? Regards --- En date de : Mar 22.11.11, Volker Lendecke <[email protected]> a écrit : De: Volker Lendecke <[email protected]> Objet: Re: [Samba] ADS Problem : segmentation fault À: "djamel boussebha" <[email protected]> Cc: [email protected] Date: Mardi 22 novembre 2011, 10h50 On Tue, Nov 22, 2011 at 09:42:20AM +0000, djamel boussebha wrote: > > I have installed vamgrind but I don't know how to use ? > Its the command "net ads join -S CINVW067 -U administrateur%laposte+1" which > generated the segmentation fault. > > I have tried : > > #vamgrind --tool=memcheck net ads join -S CINVW067 -U administrateur%laposte+1 > -bash: vamgrind: command not found > > How to use vamgrid to identify the error ? It's valgrind, not vamgrind. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
