Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Mar 1999 15:38:48 +0800
From:      Jarvis Cochrane <jarvis@guru.wow.aust.com>
To:        "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG>
Subject:   Problems with WINE  - FreeBSD bug?
Message-ID:  <36E62159.BDDFAC00@guru.wow.aust.com>

next in thread | raw e-mail | index | archive | help
Hi,

I've been trying to run multiple instances of wine 310199, installed
from the ports collection, on my FreeBSD 2.2.8 box.

(486@33Mhz, 16Mb, 2x1Gb SCSI disks)

One instance of wine will run _fine_. However, the moment a second
instance is started, the first instance exits - usually pretty cleanly,
while the second instance continues to run.

I've had some help from Ulrich Weiland (WINE) in debugging this, but he
has reached in impasse (see quoted mail below).

The first point he raised was that a semget call fails. The second point
was that the kind of behaviour my machine was exhibiting was
theoretically impossible!

Has anyone been able to run multiple instances of wine? Would anyone
like to try?

Thanks,

Jarvis

> Subject:
>           Re: Multiple instances of wine?
>     Date:
>           Fri, 5 Mar 1999 19:22:48 +0100 (MET)
>    From:
>           Ulrich Weigand Subject:
>           Re: Multiple instances of wine?
>     Date:
>           Fri, 5 Mar 1999 19:22:48 +0100 (MET)
>    From:
>           Ulrich Weigand <weigand@informatik.uni-erlangen.de>
>       To:
>           jarvis@guru.wow.aust.com
>
> > I ran wine with the debugging options you requested and tried to send
> > the output to you.
> >
> > Did you receive it ok?
>
> Yes, I received it fine.   Unfortunately I still haven't got any clue
> what could be going on here ...
>
> If you look at the end of the first trace, it is happily excuting its
> message loop (apparently receiving WM_TIMER messages regularily), when
> out of a sudden, without any other trace message, it simply fails this
> assertion (the same test which has passed hundreds of times just before).
>
> The second trace also yields no clue; it is basically identically to the
> first one, up to the point where the first one crashed and the second
> continues.
>
> So I don't know how to proceed now; unfortunately I have neither any
> experience with FreeBSD nor even ready access to a FreeBSD box.
>
> The first point I would attack is to find out exactly why the 'semget'
> call fails.  Until this is understood, everything else doesn't really
> help much ... Maybe at this point it would be useful to contact FreeBSD
> experts?
>
> Any further debugging on Wine itself would require more than just
> trace messages, I'm afraid. Do I recall correctly that you didn't
> compile Wine yourself but installed a binary version?  If you are
> interested in debugging this problem further, you'd probably need
> to compile from source so that you can use a debugger for further
> analysis ...
>
>
> Bye,
> Ulrich
>
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36E62159.BDDFAC00>