From owner-cvs-all Fri Oct 26 6: 6: 4 2001 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 63D3137B403; Fri, 26 Oct 2001 06:06:01 -0700 (PDT) Received: (from sobomax@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9QD61O73080; Fri, 26 Oct 2001 06:06:01 -0700 (PDT) (envelope-from sobomax) Message-Id: <200110261306.f9QD61O73080@freefall.freebsd.org> From: Maxim Sobolev Date: Fri, 26 Oct 2001 06:06:01 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/devel/ORBit Makefile ports/devel/ORBit/files patch-src::IIOP::giop-msg-buffer.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sobomax 2001/10/26 06:06:01 PDT Modified files: devel/ORBit Makefile Added files: devel/ORBit/files patch-src::IIOP::giop-msg-buffer.c Log: Fix a rather weird incompatibility between ORBit and FreeBSD. It appears that FreeBSD's writev(2) implementation is rather unreliable when large number of vectors is submitted - it returns EINVAL despite the fact that all arguments are pretty valid. This caused serious problems with GNOME's oaf and prevented Nautilus from working properly. The problem disappeared when I've replaced writev(2) call with appropriate loop based around ordinary write(2). Perhaps this should be investigated and the real source of the problem fixed instead, but I do not have a time for this right now. For those who interested I'm ready to provide a step-by step instruction on how to reproduce the bug. Special thanks to: andersca @ nautilus#irc.gnome.org Revision Changes Path 1.49 +1 -1 ports/devel/ORBit/Makefile 1.1 +24 -0 ports/devel/ORBit/files/patch-src::IIOP::giop-msg-buffer.c (new) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message