+1 on the option being too late. Given my dislike of silent failures, I can't object to some means of drawing attention to the problem, and failure to start certainly does that. However, there should be a way to allow the image to start in the (likely?) event that it can assist in its repair or replacement.
Bill ________________________________________ From: [email protected] [[email protected]] on behalf of Sean P. DeNigris [[email protected]] Sent: Sunday, December 04, 2011 1:46 PM To: [email protected] Subject: Re: [Pharo-project] startup errors Igor Stasenko wrote > > We invented a way to hack an image with Camillo. Instead of hacking VM :) > THis is easy and fast. > Cool! What does it mean to "hack an image"? When you wrote: Igor Stasenko wrote > > look at settings, there's already an option to save a new version of > image before quit. > if you turn this option on, then any unhandled error will open a > debugger if you open an image saved in such state. > it sounded like this would only work for experiments where you were expecting you might cause an error during startup. What I'm suggesting (and I thought the OP was requesting) is a way to recover after accidentally causing an error at startup. Now there is no way to go back in and set the setting, so the image is lost, unless you hack the VM. Or is there currently another way? -- View this message in context: http://forum.world.st/startup-errors-tp3736966p4157667.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
