| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
|
The only issue I’ve seen with FD sets in the past is listed
here: http://www.resiprocate.org/Faq#How_does_the_buildFdSet.2C_select.2C_process_loop_work.3F The last sentence reads: Warning: It is important to ensure that the FdSet you pass in to
process has been generated by a call to buildFdSet and that is has been used in
a select call - if you fail to call select then the process call will think all
file descriptors passed in are signaled, and this can cause unpredictable
behaviour. Scott From: resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of John
Gilman (johng) Hi, I'm
having a strange issue where my FdSet seems to be getting corrupted when
calling into the stack with buildFdSet() and process(). I'm
using Visual Studio 2003 to compile, and strongly suspected a problem with what
my application had FD_SETSIZE defined as versus what the sip stack it
defined as. I
tried to redefine FD_SETSIZE in my compiler project options, but no success. Does
anyone have experience/expertise in solving this issue? Thanks, -John
G |