Hi,
I've been continuing to work on my problem, where pTh raises the abort
signal because there are no threads left to schedule.
As suggested previously on this list, I've been running it under memory
checkers, and I've compiled and run it with MALLOC_CHECK defined to 2,
which immediately aborts the app when a memory violation occurs.
However, memory checkers have only turned up minor problems with STL and
the MySQL libraries. More importantly, the app is still aborting because
pTh has no threads to schedule - NOT because of a memory error. (I did
check that it aborts differently, in malloc/free, if I intentionally
introduce a memory problem.)
What might be causing pTh to think there are no threads to schedule?
Sincerely,
Brent
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
