interesting So far I’m using the sringify-ed walkbacks in emails, but (if the materializable dump isn’t too big) it would definitively be cool to have it.
Made me think, thanks for sharing Norbert & friends On Feb 26, 2014, at 11:31 AM, Norbert Hartl <[email protected]> wrote: > Here the code operates on a shared queue > > EventDispatcher>>#consumeQueue > | block | > [ true ] whileTrue: [ > block := queue next. > [ block value ] > on: Error > do: [ :err | > self serializeStackFor: err. > Log error: 'block execution failed. stack > saved' ] ] > > EventDispatcher>>#serializeStackFor: anError > [ FuelOutStackDebugAction > serializeTestFailureContext: anError signalerContext > toFileNamed: 'Stack-', (DateAndTime now printString),'.fuel' > ] > on: Error > do: [:err| "simply continue...“ ] > > Norbert > > > Am 26.02.2014 um 14:40 schrieb Esteban A. Maringolo <[email protected]>: > >> Pharo is Cool. Definitely. >> >> How do you set up the "fuel dump"? >> >> This morning I woke up with a "out of memory" crash (the first crash >> in two months), and going through the .log file didn't help much. >> >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2014-02-26 10:01 GMT-03:00 Norbert Hartl <[email protected]>: >>> The best smalltalk/pharo moments you get if you try things you want to have >>> just in order to see they are already there. >>> >>> Today FileBrowser. >>> I switched one of my servers to dump to stack with fuel to disk if an >>> exception occurs. Today I copied the files from the server to my local >>> machine and opened a workspace starting to write an expression to open >>> them. Then I thought it would be cool if I could use the file browser for >>> it. So I opened it and navigated to the directory with the fuel files...et >>> voilà...as soon as I clicked on a fuel file a button "materialize" appeared >>> which showed the stack from the server right away. >>> >>> Just brilliant! Well done! >>> >>> Norbert >> > >
