Discussion:
Strange clash of WinAPI with communications library
(too old to reply)
Yuri Feldman
2013-01-16 19:39:43 UTC
Permalink
Raw Message
Hello,

I have a strange issue using an in-house communications library.
After a certain function call (start asynchronously listening to a message) calls to the WinAPI functions Sleep, WaitForSingleObject cause a stack overflow exception.

Moreover, it seems to accumulate: the error occurs either after one call to Sleep(400) or after four calls to Sleep(100).

Any ideas what can be related?
Cholo Lennon
2013-01-16 20:16:13 UTC
Permalink
Raw Message
Post by Yuri Feldman
Hello,
I have a strange issue using an in-house communications library.
After a certain function call (start asynchronously listening
o a message) calls to the WinAPI functions Sleep, WaitForSingleObject
cause a stack overflow exception.
Moreover, it seems to accumulate: the error occurs either after one
call to Sleep(400) or after four calls to Sleep(100).
Any ideas what can be related?
Could you post some code snippet showing your communication library
usage? How about the stack trace for the exception?

Regards
--
Cholo Lennon
Bs.As.
ARG
Loading...