Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Nov 2007 20:53:40 +0100
From:      Roman Divacky <rdivacky@freebsd.org>
To:        Marcus von Appen <mva@sysfault.org>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Linuxulator on RELENG_7 causes games to hang
Message-ID:  <20071124195340.GA71917@freebsd.org>
In-Reply-To: <20071124191707.GA986@medusa.sysfault.org>
References:  <20071124091332.GA980@medusa.sysfault.org> <20071124115033.GA59527@freebsd.org> <20071124191707.GA986@medusa.sysfault.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 24, 2007 at 08:17:07PM +0100, Marcus von Appen wrote:
> On, Sat Nov 24, 2007, Roman Divacky wrote:
> 
> > On Sat, Nov 24, 2007 at 10:13:32AM +0100, Marcus von Appen wrote:
> > > Hi,
> > > 
> > > today someone reported a breakage in the linux emulation (see PR
> > > ports/118213). As games//HeroesOfMightAndMagic worked fine on RELENG_6,
> > > some change between RELENG_6 and RELENG_7 must have caused a bug with
> > > such programs.
> > > 
> > > games/HeroesOfMightAndMagic starts as supposed and goes into a wait
> > > state including a <defunct> zombie process.
> > > In contrast to other reported issues, this does not seem to be related
> > > to the sound directly (although it might be caused by it) as the process
> > > hangs no matter if sound is enabled or disabled.
> > > 
> > > games/rt2-demo suffers from the same issue, although it can be started
> > > without issues if you disable the sound with the -s parameter. 
> > 
> > please try to bisect code changes to identify the exact change that broke it.
> > I'll investigate that from that point further..
> > 
> 
> If you give me a detailled introduction about how the linux emulation
> system is organized in both, application layer, interfaces and source
> code layout, I'll gladly check through it.

just go by date... try oldest_date and see if it works, try newest_date
and see if it works. then just half the interval. bisection. you should
be able to identify day on which it broke. assigning an actual commit
that broke it should be easy.

or I dont understand your question...



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