www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: tickets #250, #254, #256 writes -> LIBSSH2_ERROR_BAD_USE ->stuck

Re: tickets #250, #254, #256 writes -> LIBSSH2_ERROR_BAD_USE ->stuck

From: Daniel Stenberg <daniel_at_haxx.se>
Date: Tue, 19 Feb 2013 23:59:27 +0100 (CET)

On Tue, 19 Feb 2013, Chris Hecker wrote:

> It just seems like requiring the exact pointer on subsequent calls is going
> to be brittle no matter what, and it's going to keep breaking in a lot of
> different ways.

I agree.

> I guess, practically speaking, is there a patch to fix the known cases of
> this bug, or a timeline for fixing it/them?

I personally am not working on this (and will not be able to within the near
future either) and I don't know of anyone else who has spoken up about it (or
in fact any of the other bugs we have reported). Feel free to dive in and give
it a go!

  / daniel.haxx.se
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2013-02-19

the libssh2 team