Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Strange clash of WinAPI with communications library
3 views
Skip to first unread message
Cholo Lennon
Jan 16, 2013, 3:16:13 PM1/16/13
to
On 16/01/2013 16:39, Yuri Feldman wrote:
> 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
> 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
0 new messages