When using smbclient to copy some backup files to an XP laptop, smbclient crashes at the same point each time. Here is the output and stacktrace: putting file Eigene Dateien/Neuer Ordner (2)/19071.pdf as \Eigene Dateien\Neuer Ordner (2)\19071.pdf (8764.3 kb/s) (average 4471.4 kb/s) Program received signal SIGSEGV, Segmentation fault. 0x00002aaaabc2b01c in malloc_consolidate () from /lib64/libc.so.6 (gdb) bt #0 0x00002aaaabc2b01c in malloc_consolidate () from /lib64/libc.so.6 #1 0x00002aaaabc2c1e6 in _int_malloc () from /lib64/libc.so.6 #2 0x00002aaaabc2db3b in malloc () from /lib64/libc.so.6 #3 0x000055555557de33 in do_put ( rname=0x555555843d10 "\\Eigene Dateien\\Neuer Ordner (2)\\~$werbung T_bingen.doc", lname=0x555555843aa0 "Eigene Dateien/Neuer Ordner (2)/~$werbung T\uffffbingen.doc", reput=0) at client/client.c:1198 #4 0x000055555557ea48 in cmd_mput () at client/client.c:1501 #5 0x000055555558362d in main (argc=Variable "argc" is not available. ) at client/client.c:3127 The x86_64 system is running FC4 with updates.
This looks like a memory corruption done earlier, not exactly in the call that segfaults. Do you have a chance to try 3.0.21c and run it under valgrind (www.valgrind.org)? The corresponding logfile most likely will give us a much better hint on what goes wrong. Thanks, Volker
I can confirm that a similar crash happens with 3.0.21c. I'll try and run it through valgrind too.
Created attachment 1782 [details] Run of 3.0.21c under valgrind, exhibiting crash condition
Comment on attachment 1782 [details] Run of 3.0.21c under valgrind, exhibiting crash condition I should point out the version of smbclient did not have debugging symbols and was running on a different system. However, it appeared to be the same crash.
updating version.
Is that still an issue in Samba 3.4.3?
I assume this is fixed. If you still see this problem with recent samba versions, please reopen or file a new bug report. Thanks!