Date: 03 Oct 2002 10:55:20 -0400 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Marc Recht <marc@informatik.uni-bremen.de> Cc: gnome@FreeBSD.org, julian@elischer.org Subject: Re: My post-vacation GNOME TODO Message-ID: <1033656921.335.5.camel@gyros.marcuscom.com> In-Reply-To: <20021003124927.43aefd7f.marc@informatik.uni-bremen.de> References: <1033572744.333.30.camel@gyros.marcuscom.com> <20021002174052.50bfc4b3.recht@contentmedia.de> <1033582816.333.63.camel@gyros.marcuscom.com> <20021003124927.43aefd7f.marc@informatik.uni-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2002-10-03 at 06:49, Marc Recht wrote: > (Julian I've cc'ed this mail to you, because I saw that the problem exists (at least on my system) since the KSE III merge and seems to be same as described in my mail from the 02/Aug.) > > > > Hmm, I coudn't build librep for ages now on -CURRENT. Themes to be thread/KSE related. lt-rep always stalls math.jl. If I "toy around" with CFLAGS/LDFLAGS like adding -pthread, setting MAKE_ENV and stuff like that I get it sometime to the point that it stalls at interpreter.jl or streams.jl. But the result is alwys that it eats all cpu and does nothing. A .jlc is never written.. > > > > Builds fine for me on today's -CURRENT. > Still no lock here. :-( I've tried with today's current and it hangs in lisp/rep/lang/interpreter.jl. > > When I drop into DDB and do a tr of the program I get nearly all of the time this: > > mi_switch(c70711a0,0,c0397db4,183,c0399940) at mi_switch+0x282 > ithread_schedule(c30dcc00,1,e8e58d3c,c7b59820,809e160) at ithread_schedule+0x122 > > sched_ithd(9) at sched_ithd+0x43 > Xintr9() at Xintr9+0x6c > --- interrupt, eip = 0x282e192a, esp = 0xbfbfbbe0, ebp = 0xbfbfbc48 --- > > And sometimes this: > > mi_switch(c30ec1a0,0,c0397db4,183,4) at mi_switch+0x282 > ithread_schedule(c7066600,1,e8e58d3c,c7b59820,809e160) at ithread_schedule+0x122 > > sched_ithd(e) at sched_ithd+0x43 > Xintr14() at Xintr14+0x6c > --- interrupt, eip = 0x282e192a, esp = 0xbfbfbbe0, ebp = 0xbfbfbc48 --- Have you updated libc_r recently? There were some issues recently with thread failures throughout -CURRENT due to changes in certain structs. The new libc_r has been quite good for my GNOME testing. As a general rule, never define NOLIBC_R if you plan on running GNOME. Joe > > Marc -- Joe Marcus Clarke FreeBSD GNOME Team :: marcus@FreeBSD.org http://www.FreeBSD.org/gnome To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1033656921.335.5.camel>