[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libthr/libkse and Mozilla Firebird



On Thu, 11 Sep 2003, Morten Rodal wrote:

> On Thu, Sep 11, 2003 at 01:57:22PM -0400, Daniel Eischen wrote:
> > On Thu, 11 Sep 2003, Morten Rodal wrote:
> > > On Thu, Sep 11, 2003 at 08:22:06AM +0800, David Xu wrote:
> > > > Did those saw Mozilla Firebird crashed test Mozilla as well ?
> > > > I used to use Mozilla, and never saw it crashed.
> > > > 
> > > 
> > > I just tested the Mozilla (www/mozilla-gtk2 ; mozilla-gtk2-1.4) port,
> > > and I can confirm that it too just disappears without a trace when run
> > > with libkse.  It also, like Mozilla Firebird, freezes (not the
> > > computer, just the app) with libthr.
> > 
> > Are you sure that your ports are correctly built (with -pthread
> > removal)?
> > 
> 
> I am pretty sure. I updated my ports tree before I compiled the Mozilla
> port.
> 
> > I'm using www/mozilla & www/mozilla-firebird.
> > 
> 
> I am recompiling mozilla-firebird right now because I have a suspicion
> that it disables the core dump unless WITH_DEBUG is defined.
> 
> > Is everyone that is having problems using NVidia cards?
> > 
> 
> Yes.  I am using nvidia cards and have, as Maximi Konovalov(?), tried
> with both the nv and the nvidia driver.  (Currently using nvidia
> driver tho)

It is possible that nvidia is detecting that an ldt has already
been allocated (calling i386_get_ldt() first before calling
i386_set_ldt()) and assumes that it (nvidia sw) has already set it.
So both the threads library and nvidia are using the same ldt
for different things and stomping on each other.

NVidia does state that their own drivers and their OpenGL will
not work with our new threads libraries (libkse/libthr).

-- 
Dan Eischen