I think we need some debugging API's in the monitor instead. BeOS nor NT has a proc file system. Hopefully this just won't be limited to Unix... Just a thought not a complaint Nick ----- Original Message ----- From: "Jens Nerche" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 20, 2000 6:36 AM Subject: GUI > > I just remember, someone would write a GUI for plex86. Seems, > this project sleeps, no? > Well, with or without this GUI it would be nice to get some > more information about the running monitor. We can provide > this information via /proc-fs, or we drop our /proc-subtree > and and provide all via GUI. Last way is better for porting, > and the only info in /proc is the number of reflected > interrupts for now. This number and some other such as > memory consumption for guest, monitor, SBE and so on, > found dangerous instructions could go into a frame of the > GUI. > Cool for debugging would be a suspend/resume mechanims > (should be easy to implement, we only don't switch to monitor > if we've our time slice) and view/change guest memory. > > Sorry for only give some ideas and code them not myself, > I've to write text for my master theses now... > > jens > >
