Re: bison-1.35 Compile error on Current

On Sun, Jun 23, 2002 at 12:50:54PM -0700, David O'Brien wrote: > I cannot reproduce either your ports/lang/gcc31 or this problem. > At this point I am suspecting something is wrong with your system. I get the same exact problem with the most recent current. This installation originally came from

statvfs() undefined ?(linux_base build problems)

Hello, I run into when building linux_base under the most recent -current: gmake[2]: Entering directory `/usr/ports/archivers/rpm/work/rpm-3.0.6/tools' /bin/sh ../libtool --mode=link cc -O -pipe -D_GNU_SOURCE -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototype

Re: Post-KSE desaster

On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > (gdb) bt > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > /usr/lib/libc_r.so.5 > #

Re: Post-KSE disaster with libc_r

On Mon, Jul 01, 2002 at 02:59:09AM -0400, Wesley Morgan wrote: > 2723 kdeinit CALL gettimeofday(0x28e94ab8,0) > 2723 kdeinit RET gettimeofday 0 > 2723 kdeinit CALL wait4(0x,0,0x1,0) > 2723 kdeinit RET wait4 2724/0xaa4 > 2723 kdeinit CALL poll(0x8059000,0x1,0) > 2723

Re: KSE status report

On Tue, Jul 02, 2002 at 10:53:23PM -0500, Erik Greenwald wrote: > I took a stab at hunting it down, I think I may've found it in the > libc_r, not the kern > > src/lib/libc_r/uthread/uthread_kern.c, in the neighborhood of line 172, > the last line of _thread_kern_sched() is > > ___longj

Re: Another KSE problem?

On Thu, Jul 11, 2002 at 09:55:51AM -0700, Julian Elischer wrote: > I have no idea what xmms is, but it seems doubtlfu that this is a KSE > problem. Hey, xmms is a very popular audio media player. BTW, I'm getting a lot of orphaned processes when I run a program in gdb and you deliver a SIGQUIT

Re: Another KSE problem?

On Thu, Jul 11, 2002 at 06:39:27PM -0700, Bill Huey wrote: > BTW, I'm getting a lot of orphaned processes when I run a program in gdb > and you deliver a SIGQUIT that seem to be stuck in poll(). It's 100 percent > repeatable. Here's a ps axl: = 1001 312

Re: Another KSE problem?

On Thu, Jul 11, 2002 at 10:58:56PM -0700, Julian Elischer wrote: > it may be in "NEW" state if it has just been forked. > if so then the "NEW" state is hanging around too long. > it should be fixed tomorrow after testing. What do you mean by just forked ? This is a running process that's block on

Re: Another KSE problem?

On Thu, Jul 11, 2002 at 11:42:56PM -0700, Julian Elischer wrote: > I was asking if it was a newly forked process... No, its not. It's something that's been running for at least a few seconds. Sorry to be unclear about that. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

ast() assert failed ?

Hello, I get a billion of these: failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for as

Re: ast() assert failed ?

On Tue, Jul 16, 2002 at 07:04:46AM +1000, Bruce Evans wrote: > Maybe. I got a few of these for my original ast() changes an instant > after I committed them (long before KSEIII), but haven't been able to > duplicate the problem (perhaps because they only occurred for SMP and > I rarely run SMP).

Re: ast() assert failed ?

On Mon, Jul 15, 2002 at 06:00:32PM -0400, Alexander Kabaev wrote: > Bruce, > > I am reliably get these messages while using gdb on user processes. This > started long before KSEIII. Right, I forgot to add that I was also running this program under gdb. I'm using the most recent -current right no