From owner-freebsd-hackers Fri Dec 29 07:10:26 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23976 for hackers-outgoing; Fri, 29 Dec 1995 07:10:26 -0800 (PST) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23971 for ; Fri, 29 Dec 1995 07:10:19 -0800 (PST) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa18431; 29 Dec 95 15:10 GMT To: freebsd-hackers@freebsd.org Subject: Linux emulator and Mathematica. X-Address: School Of Mathematics, Trinity College, Dublin 2, Ireland. X-Phone: (Home)+353-(0)1-8204643 (College)+353-(0)1-7022280 X-PGP: Public Key on Request MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6833.820249813.1@maths.tcd.ie> Content-Description: text Date: Fri, 29 Dec 1995 15:10:13 +0000 From: Colman Reilly Message-ID: <9512291510.aa18431@salmon.maths.tcd.ie> Sender: owner-hackers@freebsd.org Precedence: bulk Using a vanilla 2.1R installation: I've been trying to make Linux Mathematica using a network license,run under the linux emulator, and after adding a trivial implementation of the syslog function and hardcoding my ethernet card's address into the emulation of a socket ioctl (SIOCHWADDR) that wanted to know it (anyone want to suggest a more general way of getting this information?), I have it running to the stage previously reported by someone on the list. The problem now is that mathclient crashes. Looking at the syslog output and the system calls, it would appearing to be crashing on a sigreturn: 791 mathclient CALL sigreturn(0xefbfc0e0,0xe,0) 791 mathclient RET sigreturn -1 errno 1 Operation not permitted 791 mathclient PSIG SIGBUS SIG_DFL 791 mathclient NAMI "mathclient.core" The signal it is responding to is a sigalarm. Now, from my reading of the sigreturn stuff and the Design and Implementation of 4.3BSD, it would seem that what is happening is that the sigreturn is trying to restore some part of the state that it is not permitted to manipulate. Would this seem reasonable to the kernel experts out there? One problem with this is that when I add a debugging message at the start of sigreturn it doesn't get printed, though other processes do cause it to be printed. Any ideas on what might cause this behaviour? The current version of the linux emulator doesn't compile happily under 2.1. Colman