Matthew Lye wrote: > >>> FATAL: Assertion failure in sockets.c:2147: "is_host_addr(t->addr)" > > Could you update from SVN and see whether it still triggers?
> Yes, it does, although on 2149 instead of 2147. Is there any way to > set up the FATAL message so it has a time stamp? Just curious. That's difficult because the routine printing that has to be async-safe, so we can't just use the normal logging function. Anyway, I've committed some semi-fix to the SVN repository. After an update, you should not see such crashes anymore but only warnings. Maybe this caused by incoming connections for which the TCP handshake has not fully succeeded yet. Normally, such connections should not even be reported but some older implementations do that I think. Could you show me some of those warnings? Look for "getpeername" and "Incoming TCP connection". -- Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
