Re: Post-KSE desaster
It COULD be related to KSE if I've broken some signal delivery types.. do we have a signal guru in the house that can run a diagnostic on signals? 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Post-KSE desaster
My guess is that it's relying on getting a signal for pre-emtion and it's not arriving due to KSE breakage. 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 0x0001 in ?? () #4 0x5f28 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
Post-KSE desaster
Everything that links to libc_r is now completely hosed here, this includes all of KDE. Since KDE is a tad too big to make a handy test, here comes ogg123 from the vorbis-tools port: [lofi@kiste]:1:~ gdb ogg123 GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... (no debugging symbols found)... (gdb) run /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02Ordinary_World.ogg Starting program: /usr/local/bin/ogg123 /home/lofi/mp3/Duran_Duran/The_Wedding_A lbum/02Ordinary_World.ogg (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Device: OSS audio driver output Author: Aaron Holtzman [EMAIL PROTECTED] Comments: Outputs audio to the Open Sound System driver. Playing: /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02Ordinary_World.ogg Title: Ordinary World Artist: Duran Duran Album: The Wedding Album (no debugging symbols found)...(no debugging symbols found)...ffer 6.2% 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 ?? () Regards, -- Michael Nottebrock The circumstance ends uglily in the cruel result. - Babelfish msg40170/pgp0.pgp Description: PGP signature
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 #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
Re: Post-KSE desaster
Bill Huey wrote: Try info threads in gdb and then progressively walking through the thread list with thread N, N being the thread number. (...) Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread 3 Process 14606, Thread 3 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 2 Process 14606, Thread 2 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 * 1 Process 14606, Thread 1 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) thread 1 [Switching to thread 1 (Process 14606, Thread 1)]#0 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 ?? () (gdb) thread 2 [Switching to thread 2 (Process 14606, Thread 2)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc502 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #2 0x281ced1d in pthread_cond_timedwait () from /usr/lib/libc_r.so.5 #3 0x281c58f2 in _thread_gc () from /usr/lib/libc_r.so.5 #4 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 (gdb) thread 3 [Switching to thread 3 (Process 14606, Thread 3)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc49d in _thread_kern_sched_state () from /usr/lib/libc_r.so.5 #2 0x281c60ff in _write () from /usr/lib/libc_r.so.5 #3 0x281c6187 in write () from /usr/lib/libc_r.so.5 #4 0x2828ccc2 in ao_plugin_play () from /usr/local/lib/ao/plugins-2/liboss.so #5 0x280b4f8d in ao_play () from /usr/local/lib/libao.so.3 #6 0x08049bed in free () #7 0x0804a9a1 in free () #8 0x0804a066 in free () #9 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 As a comparison, artsd: [lofi@kiste]:0:~ gdb artsd GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... (no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/artsd (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... unix_connect: can't connect to server (unix:/tmp/mcop-lofi/kiste_localdomain-01c2-3d1fe3ca) There are already artsd objects registered, looking if they are active... ... cleaned 5 unused mcop global references. (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread * 1 Process 15847, Thread 1 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x284242e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () Regards, -- Michael Nottebrock The circumstance ends uglily in the cruel result. - Babelfish msg40172/pgp0.pgp Description: PGP signature
Re: Post-KSE desaster
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 0x0001 in ?? () #4 0x5f28 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
