On Mar 27, 2009, at 5:39 AM, Daniel Stenberg wrote:
> On Fri, 27 Mar 2009, Daniel Stenberg wrote:
>
>> Uh, I can and yes it's most probably related. I'll dig into it!
>> Thanks.
>
> Fixed now, turned out I was just stupid as usual! ;-P
I don't get the hang anymore, but I'm still getting segfaults. Both
tests fail at the same place.
make check-TESTS
/bin/sh: line 1: 30486 Segmentation fault SSHD=/usr/sbin/sshd
EXEEXT= ${dir}$tst
FAIL: simple
Fingerprint: A0 90 21 52 25 7A 06 7F B9 7B 52 CE FA A6 93 7F
Authentication methods: publickey,password,keyboard-interactive
Authentication by public key succeeded.
./ssh2.sh: line 36: 30514 Segmentation fault ./ssh2
FAIL: ssh2.sh
====================================================
2 of 2 tests failed
Please report to libssh2-devel_at_lists.sourceforge.net
====================================================
And this is the back trace for both on Mac OS X 10.5.6.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000008044
Crashed Thread: 0
Thread 0 Crashed:
0 libssh2.1.dylib 0x00051a9b libssh2_session_free +
23 (session.c:943)
1 simple 0x00001f92 main + 133 (simple.c:87)
2 simple 0x00001dda start + 54
Maybe memory getting double-freed?
Daniel
------------------------------------------------------------------------------
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel