On Tue, 2002-07-02 at 16:07, Julian Elischer wrote:
> ok, so you are saying that GNOME stuff works fine?
> What do yuo have running and is there still anything that does the wrong
> thing?

I just did an update of -CURRENT about 4 hours ago, and everything in
GNOME works fine except nautilus.  Nautilus hangs indefinitely taking up
almost all of the CPU.  Once it's killed, other GNOME apps respond
again.  This is -CURRENT kernel+world minus your recent queue.h commit.

I can get a back trace if you'd like.

Joe

> 
> On Tue, 2 Jul 2002, Wesley Morgan wrote:
> 
> > After reading this... I got to thinking, and I copied the old headers into
> > the wrong place. After rebuilding, it works fine :)... That's what I get
> > for doing it at 2am! My fault, you guys could have fixed this almost
> > immediately except for some bad info from me.
> > > Good idea.
> > >
> > > Unforunatly someone tried to complie a libc_r with the old queue.h and
> > > it had the same problem (or so they said).
> > >
> > > On Tue, 2 Jul 2002, Ian Dowse wrote:
> > >
> > >> In message
> > >> <[EMAIL PROTECTED]>, Ju
> > >> lian Elischer writes:
> > >> >The big problem at the moment is that something in the
> > >> >source tree as a whole, and probably something that came in with KSE
> > >> >is stopping us from successfully compiling a working libc_r.
> > >> >(a bit ironic really).
> > >>
> > >> Is the new
> > >>
> > >>  (elm)->field.tqe_next = (void *)-1;
> > >>
> > >> in TAILQ_REMOVE a likely candidate? That could easily tickle old bugs
> > >> in other code. The libc_r code does use a lot of TAILQ macros.
> > >>
> > >> Ian
> > >>
> > >
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-current" in the body of the message
> > 
> > 
> > 
> > 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 
-- 
PGP Key : http://www.marcuscom.com/pgp.asc

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to