Can someone please check out a libc_r tree as of 3 days ago
and try that...
There was a commit in libc_r/uthreads 2 days ago that might be relevant.
failing that, can someone try newly compiled utilities on an older pre-KSE
We need to eliminate one of these two changes...
I think it's likely that it's breakage in signals from KSE
but I'd like to know that before I tear even more hair out chasing this..
SO, I'm suffering from brain fade now..
but please, signals is known to be in dire need of cleanup
after the KSE edit, (signals are delivered to processes but can effect
individual threads. yuck)
Anyone who can help identify the problem please do.. I'm off to bed before
my head explodes..
I'll be back tomorrow AM.
I'm going to spend as much of msuspension sleeping as possible :-)
On Mon, 1 Jul 2002, Wesley Morgan wrote:
> I see this problem too. Luckily I have my entire KDE and QT system build
> with debugging symbols... However, the problem is definitely in the
> libc_r... I get virtually the same dump as Michael.
> #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5
> #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
> #2 0xd0d0d0d0 in ?? ()
> #3 0x00000001 in ?? ()
> #4 0x00005f28 in ?? ()
> On Sun, 30 Jun 2002, Bill Huey wrote:
> > 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
> > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
> > > #2 0xd0d0d0d0 in ?? ()
> > > #3 0x080570b0 in ?? ()
> > This is unlikely to be a KSE problem.
> > What do the rest of the threads look like ?
> > Try "info threads" in gdb and then progressively walking through the thread
> > list with "thread N", N being the thread number. I ran into a funny
> > create at thread start up time crash and I'm wondering if it could
> > be the same thing.
> > bill
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> _ __ ___ ____ ___ ___ ___
> Wesley N Morgan _ __ ___ | _ ) __| \
> [EMAIL PROTECTED] _ __ | _ \._ \ |) |
> FreeBSD: The Power To Serve _ |___/___/___/
> Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
> 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