Re: Libthr stable enough for testing

On Mon, 2003-05-26 at 17:51, Mike Makonnen wrote:
> Most major locking work in libthr is finished. I believe it is stable enough now
> that it can be used for most applications[1]. I would appreciate it if people
> would try it out and report any bugs.

Just installed a freshly cvsup-ped current and decided to give it a go. 
So far, everything seems to still be working (KDE, Mozilla, Evolution
are my biggest consumers of libc_r AFAICT).  artsd now works in Threaded
OSS mode (before it would just hang and never access the dsp device) and
plays mp3s much smoother.  The only indication of a problem in my ten
minutes of testing is that konsole seems to die with a signal 6 on
startup about 50% of the time.  Here's the reported backtrace:

(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)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x290456c3 in wait4 () from /usr/lib/libc.so.5
#0  0x290456c3 in wait4 () from /usr/lib/libc.so.5
#1  0x29036ab5 in waitpid () from /usr/lib/libc.so.5
#2  0x28ff2b75 in _waitpid (wpid=7, status=0x7, options=7)
    at /usr/src/lib/libthr/thread/thr_syscalls.c:396
#3  0x2867809f in KCrash::defaultCrashHandler(int) ()
   from /usr/local/lib/libkdecore.so.5
#4  <signal handler called>
#5  0x290453a3 in kill () from /usr/lib/libc.so.5
#6  0x2935ab47 in TEPty::makePty(bool) () from /usr/local/lib/konsole.so
#7  0x2935abda in TEPty::startPgm(char const*, QValueList<QCString>&,
char const*) () from /usr/local/lib/konsole.so
#8  0x2935b3fa in TEPty::commSetupDoneC() () from
/usr/local/lib/konsole.so
#9  0x28633f7d in KProcess::start(KProcess::RunMode,
KProcess::Communication)
    () from /usr/local/lib/libkdecore.so.5
#10 0x2935a426 in TEPty::run(char const*, QStrList&, char const*, bool,
char const*, char const*) () from /usr/local/lib/konsole.so
#11 0x2937eff9 in TESession::run() () from /usr/local/lib/konsole.so
#12 0x29380e89 in TESession::qt_invoke(int, QUObject*) ()
   from /usr/local/lib/konsole.so
#13 0x289be288 in QObject::activate_signal(QConnectionList*, QUObject*)
()
   from /usr/X11R6/lib/libqt-mt.so.3
#14 0x28c8cc2d in QSignal::signal(QVariant const&) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#15 0x289d7cb8 in QSignal::activate() () from
/usr/X11R6/lib/libqt-mt.so.3
#16 0x289dea73 in QSingleShotTimer::event(QEvent*) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#17 0x289614f5 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#18 0x289612be in QApplication::notify(QObject*, QEvent*) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#19 0x285ff489 in KApplication::notify(QObject*, QEvent*) ()
   from /usr/local/lib/libkdecore.so.5
#20 0x2893d727 in QEventLoop::activateTimers() ()
   from /usr/X11R6/lib/libqt-mt.so.3
#21 0x2891c861 in QEventLoop::processEvents(unsigned) ()
   from /usr/X11R6/lib/libqt-mt.so.3
#22 0x28975020 in QEventLoop::enterLoop() () from
/usr/X11R6/lib/libqt-mt.so.3
#23 0x28974f58 in QEventLoop::exec() () from
/usr/X11R6/lib/libqt-mt.so.3
#24 0x28961681 in QApplication::exec() () from
/usr/X11R6/lib/libqt-mt.so.3
#25 0x2935fbdd in main () from /usr/local/lib/konsole.so
#26 0x0804cabf in execpath_avoid_loops(QCString const&, int, char
const*, bool)
    ()
#27 0x0804d82d in execpath_avoid_loops(QCString const&, int, char
const*, bool)
    ()
#28 0x0804dcd7 in execpath_avoid_loops(QCString const&, int, char
const*, bool)
    ()
#29 0x0804ecf9 in main ()
#30 0x0804b085 in _start ()

Unfortunately I don't see any way to tell exactly what it is that is
missing the debugging symbols...

Will report back if I find anything else that isn't working.

Craig