Subject: [ libssh2-Bugs-2822910 ] send_exiting: debugdump wrong location

[ libssh2-Bugs-2822910 ] send_exiting: debugdump wrong location

From: <>
Date: Fri, 17 Jul 2009 06:17:44 +0000

This mailing list has been abandoned! Subscribe to and use the new list

Bugs item #2822910, was opened at 2009-07-17 06:17
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: misc
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: send_exiting: debugdump wrong location

Initial Comment:
In transport.c:send_existing() is the following statement

    debugdump(session, "libssh2_transport_write send()", &p->outbuf[p->osent],

at the wrong location. If debugging is enabled debugdump() may try to dump the memory at p->outbuf which is set to NULL in case the remainder of the package was sent. This cause a SigSegV.

Solution: move the statement before the "if (rc == length)"-block.


You can respond by visiting:

Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at:
libssh2-devel mailing list
Received on 2009-07-17