On Sat, 5 Dec 2009, Kamil Dudka wrote:
What does it mean actually? If you are talking about the occasional occurrence of that failure, I don't see it as problem at all. I have a reliable way to reproduce it.
Oh, I didn't realize it was somewhat easy to reproduce! Sorry for being dense.
I need to get some context info from you (e.g. where to stop debugger and what to look for). Just tell me where to start and I'll give it a try.
I'm not *really* an SSH developer, I just pretend to be one when I need to get a job done. ;-)
Seriously though, what needs to be done is getting some kind of understanding of what the code does that fails so that you can start to see where it goes wrong. I've not peronally been fiddling that much in those particular areas of the code and SSH protocol so I'm not very sure of how things run there. A good resource is of course to compare with the SSH rfc specs to learn how the packages should look like, and of course if you have a way to successfully do the same thing that's also useful.
If I would speculate, I would guess that the problem is somehow in the state machine that doesn't deal with a particular packet in some kind of situation.
-- / daniel.haxx.se _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
