6bbf7d5957
I use setjmp() to save the context just before calling bx_continue_after_config_interface(). Then, in bx_real_sim_c:quit_sim, I use longjmp() to jump back to that context. This happens in main.cc and in gui/wxmain.cc (wxWindows only). I haven't tested with the debugger yet. Possibly with debugger the quit longjmp() should jump back to the debugger prompt loop instead of actually quitting the program. - clean up BX_ASYNC_EVT_LOG_MSG implementation by creating a different, synchronous event called BX_SYNC_EVT_LOG_ASK. The async event could be used to simply tell the CI that an event has occurred, for example if the user wanted to view the events on screen (not implemented). The sync event is used when you want the user to respond before the simulation can continue, such as a for the "panic=ask" behavior. - in wxmain.cc, move the updates to the Start,Stop,Pause,Resume menu items into a separate method simStatusChanged(). This makes the code that does important stuff more readable. - remove wxMutexGuiEnter()/Leave() from MyFrame::OnSim2CuiEvent(). This method is an event handler called in the gui thread, so it already has the gui lock. This call caused thread lock on my linux box. |
||
---|---|---|
bochs | ||
bochs-performance | ||
CVSROOT | ||
sfsite |