wxYield called recursively
in [wxWindows]
|
From: Jurgen Ladstatter on 21 Apr 2008 12:20 Hi there, I'm developing a client server application using wxSocketClient and wxSocketServer. About 25% of the time when we launch the client we get a debug alert after connecting to the server: "assert wxAssertFailure failed in wxApp::Yield(); wxYield called recursively" When looking at the call stack: after the socket event, the functions wxSocketBase::Read -> ::_Read ->::WaitForRead ->::_Wait -> wxYield were called. Do you have any idea how to get rid of this error? I'm confused, because it doesn't happen all the time, neither we use threads in our application. Thanks for you help, juergen
From: Kevin Hock on 22 Apr 2008 16:52 Juergen, This is a very common issue due to the complex and powerful socket flags. I would encourage you to read a few pages from the wxWidgets book, which is available to download from here: http://www.informit.com/content/images/0131473816/downloads/0131473816_book.pdf You want to look on page 473 (in the book itself, not the PDF) under the heading "SOCKET FLAGS" (in Chapter 18) and read through the middle of page 476. I think that this will greatly help in understanding how sockets work and why you are getting this message. Kevin Hock Jurgen Ladstatter wrote: > Hi there, > > I'm developing a client server application using wxSocketClient and > wxSocketServer. About 25% of the time when we launch the client we get a > debug alert after connecting to the server: > "assert wxAssertFailure failed in wxApp::Yield(); wxYield called > recursively" > > When looking at the call stack: after the socket event, the functions > wxSocketBase::Read -> ::_Read ->::WaitForRead ->::_Wait -> wxYield were > called. > > Do you have any idea how to get rid of this error? I'm confused, because it > doesn't happen all the time, neither we use threads in our application. > > Thanks for you help, > juergen
From: Innova-Studios Juergen Ladstaetter on 23 Apr 2008 03:01 Hi kevin, thanks for your link and page numbers - that helped me a lot! Will switch to different threads now. kind regards, juergen On Tue, 22 Apr 2008 16:52:37 -0400, Kevin Hock <hockkn(a)gmail.com> wrote: > Juergen, > > This is a very common issue due to the complex and powerful socket > flags. I would encourage you to read a few pages from the wxWidgets > book, which is available to download from here: > > http://www.informit.com/content/images/0131473816/downloads/0131473816_book.pdf > > You want to look on page 473 (in the book itself, not the PDF) under the > heading "SOCKET FLAGS" (in Chapter 18) and read through the middle of > page 476. > > I think that this will greatly help in understanding how sockets work > and why you are getting this message. > > Kevin Hock > > Jurgen Ladstatter wrote: >> Hi there, >> >> I'm developing a client server application using wxSocketClient and >> wxSocketServer. About 25% of the time when we launch the client we get a >> debug alert after connecting to the server: >> "assert wxAssertFailure failed in wxApp::Yield(); wxYield called >> recursively" >> >> When looking at the call stack: after the socket event, the functions >> wxSocketBase::Read -> ::_Read ->::WaitForRead ->::_Wait -> wxYield were >> called. >> >> Do you have any idea how to get rid of this error? I'm confused, because > it >> doesn't happen all the time, neither we use threads in our application. >> >> Thanks for you help, >> juergen > > _______________________________________________ > wx-users mailing list > wx-users(a)lists.wxwidgets.org > http://lists.wxwidgets.org/mailman/listinfo/wx-users
|
Pages: 1 Prev: Re[2]: wxString threadsafe? Next: Using native windows calls inside wxwidgets. |