Sean,
I am not a regular Pharo user, so I have no code example for you. Just an idea:
why not save an image copy instead of the image itself? Thus if an error occurs
that might not happen at next startup (external dependencies etc.) , you couldÂ
restart the "real image" and still use the failed
Hi Sean,
You can always try:
exception freeze.
freeze will copy the stack so it is usable in a posterior debug session
even if the original contexts died.
exception debug.
Opens a debugger :)
On Mon, Nov 13, 2017 at 5:20 PM, Sean P. DeNigris
wrote:
> Tim Mackinnon wrote
> > you can overri
Tim Mackinnon wrote
> you can override this and Fuel out the debug context to a file
Thanks, Tim! I do know about that, but I was thinking/hoping that maybe
there was a way to keep the debug context alive without fueling out…
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltal
I do something similar, in my WAHtmlHaltAndErrorHandler subclass
fuelOutException: exception
| filename context |
filename := 't3-seaside-exception-{1}.fuel' format: { ZTimestamp now
format: '20010203T160506' }.
context := exception signalerContext.
[ FuelOutStackD
Hi Sean - not sure if this is exactly what you are after, but there is a method
in the debugger that is invoked when you need to debug, you can override this
and Fuel out the debug context to a file (or I guess even a variable in the
image if you are also saving the image when it gets an error).
Sean P. DeNigris wrote
> In a headless image, I'd like to do the following: if there's any error,
> arrange to have a debugger open on the next (headful) launch, and then
> save
> and quit.
Bump :) I can't believe no one knows how to do this!
-
Cheers,
Sean
--
Sent from: http://forum.world
Some of this can be seen in VA Smalltalk. Errors during start up are
captured and can be debugged after the start up has completed.
The idea of an Error Queue Viewer is a nice touch, along with the
possibility of remote debugging.
On Nov 7, 2017 6:55 PM, "Ben Coman" wrote:
On Wed, Nov 8, 20
On Wed, Nov 8, 2017 at 10:16 AM, Sean P. DeNigris
wrote:
> In a headless image, I'd like to do the following: if there's any error,
> arrange to have a debugger open on the next (headful) launch, and then save
> and quit.
>
> I'm drawing a blank - how would I do that?
>
> I explored various dead
In a headless image, I'd like to do the following: if there's any error,
arrange to have a debugger open on the next (headful) launch, and then save
and quit.
I'm drawing a blank - how would I do that?
I explored various dead ends, the culmination of which was the
image-breaking:
actualWorkBloc
