Date: Thu, 12 Apr 2012 23:04:16 +0400 From: Solar Designer <solar@...nwall.com> To: owl-dev@...ts.openwall.com Subject: Re: lftp update On Thu, Apr 12, 2012 at 10:43:09PM +0400, Solar Designer wrote: > lftp: Torrent.cc:119: Torrent::Torrent(const char*, const char*, const char*): Assertion `my_peer_id.length()==PEER_ID_LEN' failed. > Aborted > > This is only seen in the x86_64 build, but not in the i686 build. > > I suggest that we start by updating lftp in Owl-current to latest, then > if there are no issues with it for a while just include this update into > 3.0-stable as well. This will likely eliminate the need for > investigating and patching the above issue separately (I guess it is > already fixed upstream). I've just tried building 4.3.6 from source, and the problem is still there. So I've investigated it. Turns out that it's not x86_64 vs. i686 that made the difference, but rather the PID of the lftp process did. I've attached a patch that we'll need to include. I'll also report this upstream. Alexander View attachment "lftp-4.3.6-owl-torrent-my_peer_id.diff" of type "text/plain" (474 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.