From owner-freebsd-openoffice Fri Oct 25 7:58: 8 2002 Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7550A37B401 for ; Fri, 25 Oct 2002 07:58:07 -0700 (PDT) Received: from lastebil.math.ntnu.no (lastebil.math.ntnu.no [129.241.211.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 18D3243E3B for ; Fri, 25 Oct 2002 07:58:05 -0700 (PDT) (envelope-from perchrh@stud.math.ntnu.no) Received: (qmail 10971 invoked from network); 25 Oct 2002 14:58:05 -0000 Received: from mona.math.ntnu.no (129.241.211.204) by lastebil.math.ntnu.no with QMQP; 25 Oct 2002 14:58:05 -0000 Date: Fri, 25 Oct 2002 16:58:02 +0200 (CEST) From: Per Christian Henden X-X-Sender: perchrh@mona.math.ntnu.no To: openoffice@FreeBSD.ORG Subject: OpenOffice in ports: usage of /proc/ In-Reply-To: <20021013165529.W15308-100000@levais.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-openoffice@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm using a FreeBSD system with no /proc filesystem, and because of this (I think) openoffice from ports segfaults. ktrace /usr/local/OpenOffice.org1.0/setup and kdump reveals: 6587 setup.bin CALL getpid 6587 setup.bin RET getpid 6587/0x19bb 6587 setup.bin CALL open(0xbfbfd400,0,0) 6587 setup.bin NAMI "/proc/6587/cmdline" 6587 setup.bin RET open -1 errno 2 No such file or directory 6587 setup.bin CALL getpid 6587 setup.bin RET getpid 6587/0x19bb 6587 setup.bin CALL open(0xbfbfe080,0,0) 6587 setup.bin NAMI "/proc/6587/cmdline" 6587 setup.bin RET open -1 errno 2 No such file or directory 6587 setup.bin PSIG SIGSEGV SIG_DFL 6587 setup.bin NAMI "core" The patch patch-sal+osl+unx+system.h in (todays) ports-stable and ports-current editors/openoffice/files/ contains the line +# define CMD_ARG_PROC_NAME "/proc/%u/cmdline" This is the reason for the segfault as far as I can see. Is it possible to do without the use of /proc? If not there should be a check to see if /proc is mounted/is enabled in the kernel/has some files inside of it before the program assumes it is. I should fix this myself, I know, but I don't know C/C++ :( -- Per Christian Henden, perchrh@stud.ntnu.no --------------------- Why don't elephants eat penguins ? Because they can't get the wrappers off ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-openoffice" in the body of the message