From owner-freebsd-emulation Mon Dec 7 11:42:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05142 for freebsd-emulation-outgoing; Mon, 7 Dec 1998 11:42:46 -0800 (PST) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05137 for ; Mon, 7 Dec 1998 11:42:41 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id NAA11122 for ; Mon, 7 Dec 1998 13:42:37 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812071942.NAA11122@ns.tar.com> From: "Richard Seaman, Jr." To: "emulation@freebsd.org" Date: Mon, 07 Dec 98 13:42:37 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: linux_pipe, broken? Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is the pipe call in linux emulation (linux_pipe) broken? I've been experimenting with getting linux threads running in linux emulation mode. Linux threads creates a thread manager thread and uses a pipe to communicate requests for thread creation and termination to the thread manager. It appears that the thread manager gets corrupted data when it reads from the pipe. The thread manager thread appears to be created ok, and hangs when it gets a bad address in data read from the pipe (why it doesn't seg fault is beyond me -- the address it gets in the data is 0x4, which happens to be the fd of the write end of the pipe, the read end is 0x3). Also, I tried getting StarOffice 5.0 running, and the setup program seg faults immediately after executing a pipe call, before linux threads is started. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message