Or, change de default "main.c" so the system executes some very simple endless task (i.e. just printing "Hello World" in an endless loop) that may be more "beatiful" than a system crash due to cap violation.
El sáb, 29 may 2021 a las 8:50, Roderick Chapman (<[email protected]>) escribió: > On 29/05/2021 06:08, Gerwin Klein wrote: > > If you edit on GitHub, this will ultimately raise a pull request on the > markdown file that backs that particular change, and will be reviewed by > someone with (hopefully ;-)) more knowledge. So there is no danger of > breaking anything by accident. > OK... sounds good. > > > > For tutorials, there tend to be two "edit" links, because text gets > included from multiple sources. One link is for the main page, and one for > the included text, linking to the repository it comes from (it should say > something like "Tutorial included from [github repo]. [edit]") > > > > I'm happy to do the edit, though. Just to double check, you mean the > pagehttps://docs.sel4.systems/Tutorials/hello-world.html ? > Yes.. that one. > > > > What would make sense to add at the bottom to be less confusing? > > It would be good to tell the reader to expect the run to end with a > capability violation and a stack dump, and then "Ctrl-A, X" is needed to > terminate QEMU. > > - Rod > > > > _______________________________________________ > Devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
