[Glass] GsDevKit and tode debugger
Mariano Martinez Peck via Glass
glass at lists.gemtalksystems.com
Mon Sep 17 07:59:23 PDT 2018
This is what I used to do:
http://forum.world.st/Debugging-a-multiple-process-system-tp5063742p5063833.html
Maybe it helps too.
Cheers,
On Wed, Sep 12, 2018 at 12:50 AM Jon Paynter via Glass <
glass at lists.gemtalksystems.com> wrote:
> Thanks for the workspace cmd. That will make things a lot easier.
> debugging via topaz is not pleasant.
>
> On Tue, Sep 11, 2018 at 7:58 PM, Jupiter Jones <jupiter.jones at mail.com>
> wrote:
>
>> For running code you can open a workspace with ‘ws’ and use that.
>>
>> Or if you use the script a lot, you can create a tODE script node with
>> ‘touch st myScriptName’, then edit it with 'edit myScriptName’. That opens
>> a workspace to use as well. There’s probably a way to run those scripts
>> from the tODE shell, but I can’t remember it right now.
>>
>> Sorry I can’t help with the error. I remember having a similar issue with
>> REST and from memory ended up adding my own debugging hander something like:
>>
>> [ self doMyRestThing ] on: Error do: [ :error |
>> GRPlatform current doTransaction: [
>> (ObjectLogEntry
>> error: ‘Something screwed up’
>> object: (Array with: error with: otherThingUsefulForDebugging)) addToLog
>> ]
>> ]
>>
>> I’m not at my dev machine right now so I don’t know if the above code is
>> right, but hopefully help.
>>
>> Cheers,
>>
>> J
>>
>> On 12 Sep 2018, at 12:38 pm, Jon Paynter via Glass <
>> glass at lists.gemtalksystems.com> wrote:
>>
>> Hi All,
>>
>> Im starting a new project with GsDevKit and glass as the backend server.
>> The idea is to use the seaside REST interface to communicate to my UI layer.
>>
>> Installation went MUCH better than last time i tried this. Kudos to Dale
>> for getting everything running smoothly. Im running gemstone v 3.2.10
>>
>> I have a tode client running on my windows PC, which connects to stone
>> running in a ubuntu VM. I can write code just fine and see it serve up my
>> REST calls. but when it comes to trying to debug anything, its not working.
>>
>> my expectation is when an exception occurs -- I should see a continuation
>> in the object log. instead all I see in the object log is a message saying
>> topaz has quit.
>>
>> at first I thought it was due to my choice of error handler in the
>> seaside config for my rest service. but all of them have the same results.
>>
>> See attached the zinc_server log file -- I put a 'self halt' in my domain
>> code.
>>
>>
>> Also on a (possibly?) related note, I cant figure out how to run
>> arbitrary code in gemstone from the tode client. I tried using the 'eval'
>> command but that always gives me a compile error. And using the 'do it'
>> option from within a code browser has no effect.
>>
>> eval 'Array new' ==>
>> a CompileError occurred (error 1001), compilation errors -- parameter 1
>> is error descriptor
>> --------------------
>> 1. CompileError(AbstractException)>>_outer:with: @8 line 19
>> 2. CompileError(AbstractException)>>outer @2 line 19
>> 3. [] in UndefinedObject(TDAbstractEnvironment)>>_compileBlock: @9 line 11
>> 4. Array(Collection)>>do: @5 line 10
>> 5. [] in TDStandardEnvironment(TDAbstractEnvironment)>>_compileBlock: @4
>> line 8
>> 6. CompileError(AbstractException)>>_executeHandler: @3 line 8
>> 7. CompileError(AbstractException)>>_signalFromPrimitive: @1 line 1
>> 8. String>>_compileInContext:symbolList:oldLitVars:environmentId: @1 line
>> 1
>> 9. String>>_compileInContext:symbolList:oldLitVars:environmentId:flags:
>> @2 line 3
>> 10. [] in
>> UndefinedObject(TDAbstractEnvironment)>>_compile:inContext:literalVars:tempSymbolList:environmentId:
>> @3 line 5
>> 11. [] in TDStandardEnvironment(TDAbstractEnvironment)>>_compileBlock: @3
>> line 2
>> 12. TDStandardEnvironment(ExecBlock)>>on:do: @3 line 42
>> 13. TDStandardEnvironment(TDAbstractEnvironment)>>_compileBlock: @3 line 3
>> 14.
>> TDStandardEnvironment(TDAbstractEnvironment)>>_compile:inContext:literalVars:tempSymbolList:environmentId:
>> @2 line 3
>> 15.
>> TDStandardEnvironment(TDAbstractEnvironment)>>compile:inContext:literalVars:tempSymbolList:environmentId:
>> @2 line 3
>> 16.
>> TDStandardEnvironment(TDAbstractEnvironment)>>evaluate:in:literalVars:tempSymbolList:environmentId:
>> @2 line 3
>> 17.
>> TDTopezServer>>evaluateString:inContext:literalVars:withTempSymbolList:environmentId:
>> @4 line 5
>> 18. [] in TDShellTool>>eval @6 line 15
>> 19. OrderedCollection(Collection)>>do: @5 line 10
>> 20. TDShellTool>>eval @5 line 11
>> 21. TDShellTool class(TDAbstractDevTool
>> class)>>performCommand:withSelector:objIn:commandOptions:todeCommand: @14
>> line 10
>> 22. TDShellTool class(TDAbstractDevTool
>> class)>>performCommand:objIn:commandOptions:todeCommand: @2 line 3
>> 23. [] in TDShellTool class>>eval @2 line 5
>> 24. TDShellTool class(ExecBlock)>>cull:cull:cull:cull: @7 line 4
>> 25. TDTopezServer>>evaluateCommand:objIn: @18 line 22
>> 26. TDTopezServer>>evaluateSTONCommand: @9 line 6
>> 27. Executed Code
>> 28. GsNMethod class>>_gsReturnToC @1 line 1
>>
>>
>> Ideas and suggestions on how to solve these would be much appreciated
>> <zinc_server.log>_______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>>
>>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
--
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20180917/cd23108d/attachment.html>
More information about the Glass
mailing list