Subject: Re: current pthread/sa buglist
To: Dublet <>
From: sudog <>
List: current-users
Date: 02/17/2003 11:03:11
On Monday 17 February 2003 10:05, Dublet wrote:
> I have gotten the same response.
> Here's some gdb output after it ceased playing:
> #0  0x4856525f in poll () from /usr/lib/
> #1  0x482e1fae in poll () from /usr/lib/
> #2  0x482f8713 in g_main_poll () from /usr/local/lib/
> #3  0x482f80de in g_main_iterate () from /usr/local/lib/
> #4  0x482f847c in g_main_run () from /usr/local/lib/
> #5  0x482016db in gtk_main () from /usr/X11R6/lib/
> #6  0x80844c7 in main ()
> #7  0x8058e44 in ___start ()

This is interesting. I've seeing segfaults in _sys_poll, pthread__switch(), 
and a few other interesting places in a QT application I'm (failing) to port 
and fix to work with the new sa stuff. It seemed to work fine under the old 
pth regime.

Have to try a new -current and see what's what. Probably an application error: 
no comments makes for a long time tracing logic. Curse programmers who refuse 
to comment obfuscated C++ software.