I saw the screencast where Mariano did something like that. I had just built the image, when the original VM crash happened, so it wasn't that much of a deal to rebuild it.
I would like to see some form of safe-mode boot for Pharo, so that just the kernel would be loaded. ST images are all about state, and when production servers go down, it would be nice to be able to start them up, and rewind the app. For normal apps this is not an issue, but when forking processes for socket IO or a FFI call, it is possible to bring it down (or in my case where I think my error handling code caused an error) , and moving in a backup image is not always enough. I would like to get involved in such a project, if there was interest for it. On Fri, Sep 9, 2011 at 18:41, Sean P. DeNigris <[email protected]> wrote: > > John Toohey wrote: >> >> So do I have to rebuild a new image from scratch now? Is there any >> command line switch that I can use to by pass the loading of my app on >> start up? >> > > I don't know if it'd be worth it, but if you're talking about a lot of work > lost, it sounds like you could build a debug VM and bypass the loading code > from the debugger (like I just had to do). > > Sean > > -- > View this message in context: > http://forum.world.st/1-3-OneCick-with-Cog-VM-tp3798884p3802970.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- ~JT
