*BSD News Article 82049


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!news.stealth.net!news.ibm.net.il!arclight.uoregon.edu!dispatch.news.demon.net!demon!prds-grn.demon.co.uk!prds-grn!t.d.g.sandford
From: t.d.g.sandford@prds-grn.demon.co.uk (Thomas D.G. Sandford)
Newsgroups: comp.emulators.ms-windows.wine,comp.unix.bsd.freebsd.misc
Subject: Re: Wine960928 crashed FreeBSD 2.1.5
Followup-To: comp.emulators.ms-windows.wine,comp.unix.bsd.freebsd.misc
Date: 30 Oct 1996 23:39:11 GMT
Organization: Paradise Green Technical Services
Lines: 42
Message-ID: <558ouv$2a1@prds-grn.demon.co.uk>
References: <32762988.167EB0E7@watermarkgroup.com>
NNTP-Posting-Host: localhost.demon.co.uk
X-NNTP-Posting-Host: prds-grn.demon.co.uk
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.emulators.ms-windows.wine:5856 comp.unix.bsd.freebsd.misc:30403

Luoqi Chen (luoqi@watermarkgroup.com) wrote:
: Wine crashes my machine whenever I try to do "wine -help", or try to
: run any non-existing file. It seemed that the CPU reset without any
: panicking message. Does anyone else have this problem? Is it unique to
: FreeBSD? How does wine crash the system without causing a panic?

: The last message on screen was "wine: can't exec '-help'". I looked
: at wine source code, there is only a printf statement followed by
: an exit. Printf didn't show maybe because it's still in buffer.
: The only way exit could crash the system was the atexit calles,
: which include a XChangeKeyboard and winsock cleanup, none looked
: likely to be the cause. I'm really puzzled. Any help is appreciated.

It is (I think) a FreeBSD problem. It occurs when wine executes the fork()
in loader/module.c

Actually it does usually cause a printed panic (panic: setrunqueue) - but
the panic message appears on vt1, whereas you are looking at vt4 (the X vt).
You can see the panic message by running wine from vt1 thus:

<on vt1>
startx &
<when X has started, switch back to vt1 with <ctrl><alt><f1> >
setenv DISPLAY :0.0
wine nosuchfile

The same problem occurs with FreeBSD 2.1.0-RELEASE, and I have logged it with
the FreeBSD development team (kern/1118).

A temporary fix is to replace the line 

	if (!fork())

with

	if (0)

This at least prevents your machine from rebooting.

--
Thomas Sandford | t.d.g.sandford@prds-grn.demon.co.uk
Paradise Green Technical Services: S'ware/Hw design and Theatre Tech. Services