Serializing Excpetion with Fuel on the production and opening debugger on the dev machine - hot to? [Pharo 5]
Hello, what is the current procedure for achieving %subj%? I am on latest Pharo 5. I am serializing server side exception with: FLSerializer serialize: anException toFileNamed: 'something'. But how to open a debugger after materialization on the "dev machine side"? I found (Google, Mailing list) some examples, but it's obsolete (the debugger class no longer exists in Pharo 5 etc etc). Thanks! Petr Fischer
PharoLambda does this - Iâm not near a computer to extract the code, but if you need it quickly you should find it easily - there is a class method on Lambda - something like debugSavedS3 which shows how to read in a file (from S3) and then launch a debugger. Tim Sent from my iPhone
On 10 May 2018, at 10:58, Petr Fischer <petr.fischer@me.com> wrote:
Hello, what is the current procedure for achieving %subj%? I am on latest Pharo 5.
I am serializing server side exception with:
FLSerializer serialize: anException toFileNamed: 'something'.
But how to open a debugger after materialization on the "dev machine side"?
I found (Google, Mailing list) some examples, but it's obsolete (the debugger class no longer exists in Pharo 5 etc etc).
Thanks! Petr Fischer
Hereâs the snippet to open a debugger (used in Pharo 6 tho) materializedContext := (FLMaterializer newDefault materializeFrom: gzip) root. sessionName := 'debug saved Fuel context: {1}' format: {aName}. GTGenericStackDebugger openOn: ((Process forContext: materializedContext priority: Processor userInterruptPriority) newDebugSessionNamed: sessionName startedAt: materializedContext). Tim Sent from my iPhone
On 10 May 2018, at 12:41, Tim Mackinnon <tim@testit.works> wrote:
PharoLambda does this - Iâm not near a computer to extract the code, but if you need it quickly you should find it easily - there is a class method on Lambda - something like debugSavedS3 which shows how to read in a file (from S3) and then launch a debugger.
Tim
Sent from my iPhone
On 10 May 2018, at 10:58, Petr Fischer <petr.fischer@me.com> wrote:
Hello, what is the current procedure for achieving %subj%? I am on latest Pharo 5.
I am serializing server side exception with:
FLSerializer serialize: anException toFileNamed: 'something'.
But how to open a debugger after materialization on the "dev machine side"?
I found (Google, Mailing list) some examples, but it's obsolete (the debugger class no longer exists in Pharo 5 etc etc).
Thanks! Petr Fischer
Thanks to all! Works perfectly! pf
Hereâs the snippet to open a debugger (used in Pharo 6 tho)
materializedContext := (FLMaterializer newDefault materializeFrom: gzip) root.
sessionName := 'debug saved Fuel context: {1}' format: {aName}.
GTGenericStackDebugger openOn: ((Process forContext: materializedContext priority: Processor userInterruptPriority) newDebugSessionNamed: sessionName startedAt: materializedContext).
Tim
Sent from my iPhone
On 10 May 2018, at 12:41, Tim Mackinnon <tim@testit.works> wrote:
PharoLambda does this - Iâm not near a computer to extract the code, but if you need it quickly you should find it easily - there is a class method on Lambda - something like debugSavedS3 which shows how to read in a file (from S3) and then launch a debugger.
Tim
Sent from my iPhone
On 10 May 2018, at 10:58, Petr Fischer <petr.fischer@me.com> wrote:
Hello, what is the current procedure for achieving %subj%? I am on latest Pharo 5.
I am serializing server side exception with:
FLSerializer serialize: anException toFileNamed: 'something'.
But how to open a debugger after materialization on the "dev machine side"?
I found (Google, Mailing list) some examples, but it's obsolete (the debugger class no longer exists in Pharo 5 etc etc).
Thanks! Petr Fischer
Am 10.05.2018 um 11:58 schrieb Petr Fischer <petr.fischer@me.com>:
Hello, what is the current procedure for achieving %subj%? I am on latest Pharo 5.
I am serializing server side exception with:
FLSerializer serialize: anException toFileNamed: 'something'.
But how to open a debugger after materialization on the "dev machine side"?
I found (Google, Mailing list) some examples, but it's obsolete (the debugger class no longer exists in Pharo 5 etc etc).
Thanks! Petr Fischer
Have a look at FuelOutStackDebugAction>>#serializeTestFailureContext:toFileNamed: Hope this helps! Norbert
participants (3)
-
Norbert Hartl -
Petr Fischer -
Tim Mackinnon