Bryce Denney 84c33ec824 - I was getting occasional thread bugs and crashes when I click on ... Quit while the simulation was running. I used to just do wxFrame::Close(TRUE) in the wxwindows thread, but the simulation thread would keep on running even after the window had disappeared. If the simulation thread sent any messages to the gui, it could segfault. Now, when you click on Quit it asks the simulator to quit, but does not close the gui. When the simulator thread finally quits, THEN it calls wxFrame::Close(TRUE) from the sim_thread (with appropriate gui mutex). Such tricks are only needed when the simulation is running. I hope this will fix bug #616142: "wx: crash from events after gui shutdown". - move MyFrame::closing flag out into a global variable wxBochsClosing so that it will be valid even when the MyFrame is deleted. See comments on in wxmain.h. - when wxBochsClosing is set, don't create any new windows. If any errors appear, just print them to stderr because the gui is just about to be closed. - fix comment in SimThread::Entry to talk about longjmp instead of kill_bochs_request - (minor) move contents of DefaultCallback2 into DefaultCallback. It doesn't refer to the wxApp at all. This is a bit safer in case it gets called when the wxApp is in the process of being deleted. - modified: gui/wxmain.cc gui/wxmain.h		2002-10-07 04:01:00 +00:00
bochs	- I was getting occasional thread bugs and crashes when I click on	2002-10-07 04:01:00 +00:00
bochs-performance	- add comments describing how blur-translate works	2002-04-17 22:51:58 +00:00
CVSROOT	- fixing { parameter	2002-03-21 07:15:06 +00:00
sfsite	- add warning that many disk images are out of date	2002-09-30 21:01:39 +00:00