I'm glad to hear I'm not insane, or a really bad programmer... :0
I've traced my case of this misfortune back to a call to close a socket.
When the sockets are left open indefinitely, the app works fine; when
closed, it bombs out thinking that there are no threads to schedule. As
with Shawn's app, the thread stack sizes are far bigger than they really
need to be. Maybe this will trigger some ideas as to what is wrong?
Sincerely
Brent
At 02:22 PM 7/23/2001 -0700, you wrote:
>On Thu, Jun 28, 2001 at 09:59:38AM -0700, Archie Cobbs wrote:
> > Brent Phillips wrote:
> > > As a follow-up thought to the letter below, how will pTh behave if a
> thread
> > > stack isn't big enough? Will it raise the abort signal thinking it has no
> > > threads to schedule? Or would exit in some other manner?
> >
> > I'd imagine anything is possible in that scenario.
> >
> > In these situations the only thing left to do is start trimming
> > the program down to the minimal amount of code that reproduces
> > the problem...
>
>I'm having the same problem, with stack sizes set to far over what the
>threads are using, so I don't think that is the problem.
>
>The main thread is blocking in a pth_join.
>Another thread is blocking in a pth_accept.
>Another is in the middle of a pth_select with a 1 second timeout.
>The last is entering a pth_select when the scheduler breaks.
>
>I'll try to duplicate this in a minimal test case.
>
>--
>Shawn Wagner
>[EMAIL PROTECTED]
>______________________________________________________________________
>GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager (Majordomo) [EMAIL PROTECTED]
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
