When this thread began, I initially assumed that the system header file
would implement FD_SET (etc.) by either checking itself whether
the socket number was in the range [0,FD_SETSIZE), or else by ensuring that it
would use a bitmap large enough for all possible socket numbers (regardless of
> Yes, I suppose I could add a test for “socketNum >= FD_SETSIZE” to
> “BasicTaskScheduler::setBackgroundHandling()” (note that there’s already a
> test for “socketNum < 0”). I would have thought/hoped that FD_SET() would
> have already tested for this, but perhaps not...
>
> This is all assum
> socket() can give a number above FD_SETSIZE (FD_SETSIZE is a limit for fd_set
> used by select(), but is not related to socket()).
Yes, you’re right; my mistake.
Yes, I suppose I could add a test for “socketNum >= FD_SETSIZE” to
“BasicTaskScheduler::setBackgroundHandling()” (note that there’s
Michel.
[@@ THALES GROUP INTERNAL @@]
De : live-devel [mailto:live-devel-boun...@ns.live555.com] De la part de Ross
Finlayson
Envoyé : mercredi 10 décembre 2014 15:20
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] Problem using live555MediaServer with more than 250
> In order to avoid to reach the abort, I try an extra sanity check inside
> BasicTaskScheduler::setBackgroundHandling
> void BasicTaskScheduler::setBackgroundHandling(int socketNum, int
> conditionSet, BackgroundHandlerProc* handlerrProc, void * clientData) {
> if ( (socketNum <0) || (socketNum
