Hi Christian!

Did you succeed running this version?

I tried it on a lenny system (64bit). cifs.upcall -v gives a segmentation fault:
(gdb) run
Starting program: /tmp/cifs-utils-4.7/cifs.upcall -v
[Thread debugging using libthread_db enabled]
version: 4.7
[New Thread 0x2ab76635bc90 (LWP 14118)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2ab76635bc90 (LWP 14118)]
0x00002ab765416a65 in free () from /lib/libc.so.6
(gdb) bt
#0  0x00002ab765416a65 in free () from /lib/libc.so.6
#1  0x0000000000402854 in main (argc=<value optimized out>, argv=<value optimized 
out>) at cifs.upcall.c:815


Simular errors on two testing systems (64bit):
s...@pc01:~$ cifs.upcall -v
version: 4.7
*** glibc detected *** cifs.upcall: free(): invalid pointer: 0x0000000000401014 ***
======= Backtrace: =========
/lib/libc.so.6(+0x71ad6)[0x7f2058cb5ad6]
/lib/libc.so.6(cfree+0x6c)[0x7f2058cba84c]
cifs.upcall[0x4028b5]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7f2058c62c4d]
cifs.upcall[0x401c79]


So something is not right here.

Shade and sweet water!

        Stephan

--
| Stephan Seitz             E-Mail: s...@fsing.rootsland.net |
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |

Attachment: signature.asc
Description: Digital signature

Reply via email to