happens to me too... left a paused game of Mig29m Superfulcrum there for half an hour and came back... dosemu froze.
----- Original Message ----- From: "Stas Sergeev" <[EMAIL PROTECTED]> To: "David Milligan" <[EMAIL PROTECTED]> Sent: Saturday, October 06, 2001 12:25 AM Subject: Re: dosemu sessions crashing after 30 mins of keyboard inactivity > "David Milligan" wrote: > > Some of our (and others) programmes appear to either "crash" or "pause" if > > they are left running for around 30 minutes or more. > Is this with dosemu-1.0.2? > > > This is especially apparent in our programmes which have a screen saver > > feature. The screen saver routine is pretty simple and does some screen > > writes, keyboard idle loop, and some Novell semaphore checking. It does also > Are you playing with timer's speed? Are you using timer-related delays? > > > I haven't determined conclusively what happens but sometimes the programmes > > get "stack overflow" errors, sometimes just lock permanently, sometimes get > Seems like PIC problems again... > > > Some more tidbits :- > > get out of screen saver or something else) the CPU util in TOP for that > > DOSEMU session goes up to >90%. Tracing system calls, it repeats a sequence > > of vm86() calls over and over. > This is "normal" behavior. > > > While a fix for this behaviour would be good a "fudge" such as putting some > > kind of dumby key press in the dosemu keyboard source may get around this. > You can try to implement such a workaround but I doubt you will ever get it > into the official version (just IMHO). > > > Can anyone point me in the direction of what to do here? > Well, in case you are really going to fix it, you should start with the > following: > - apply the attached patch. It will increase the log file limit up to 30Mb and > make it circular, else dosemu will just exit when log size reach 10Mb (patch > untested). > - make a log: dosemu -D9+grI -o /tmp/dosemu.log > - as the PIC implementation is very buggy, it would be a good idea to > make a separate log for PIC with -D9+r option. I beleave that the PIC is the > root of all evil for a *random* crashes and stack overflows. > Ok, making everything mentioned above should be a good starting point > for hunting such a bug. The logs should give you a clue such as what is failing. > - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
