[Glass] Debugging in GemTools and "undefined symbol"

[Mariano Martinez Peck]

On Tue, Dec 17, 2013 at 12:50 PM, Dale K. Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

>
>
> ------------------------------
>
> *From: *"Mariano Martinez Peck" <marianopeck at gmail.com>
> *To: *"Johan Brichau" <johan at yesplan.be>
> *Cc: *glass at lists.gemtalksystems.com
> *Sent: *Tuesday, December 17, 2013 7:03:09 AM
> *Subject: *Re: [Glass] Debugging in GemTools and "undefined symbol"
>
>
>
>
>
> On Tue, Dec 17, 2013 at 11:48 AM, Johan Brichau <johan at yesplan.be> wrote:
>
>> I'm afraid these are things you get used to in gemtools :-/
>>
>
> Ok, I feel better I am not the only one ;)
>
>
>> Luckily, it's not the place to develop most of your code...
>>
>>
> Indeed.
>
> But my question was more about if it was a problem of GemTools (hoping
> tODE could solve this)  or a more technical problem (like context
> reification , debugger temp map, etc...)
>
> Frankly I don't recall the technical reason that temps
>

Actually is neither temps or instance variables. The only thing I seem to
have access to is "self".


> were not made available in the GemTools debugger ... our compiler is
> written in C and does not have as many entry points as the Pharo compiler
> so "faking a method context" when doing evaluation within debugger frame
> could be a bit difficult to accomplish ... then again, I might not have
> been smart enough when I wrote the debugger chunk ...
>

I can imagine the difficulties, that's why I asked ;)

OK, so at least you confirm the limitations and I am not doing something
wrong.


>
> I haven't added menus to the text windows yet in tODE, but now that you've
> mentioned this I will take a closer look at making this happen in tODE ...
>
>
I don't know what you mean by "added menus to the text windows".
For me, there most important thing from GemTools is the ability to debug a
problem from the ObjectLog. So..that's why I would like the most from tODE:
the debugger.

Thanks!


> Dale
>
>
> Thanks!
>
>
>> Johan
>>
>> On 17 Dec 2013, at 14:07, Mariano Martinez Peck <marianopeck at gmail.com>
>> wrote:
>>
>> > Hi guys.
>> >
>> > While I am debugging from GemTools I notice that the debugger
>> facilities are quite different that from say Pharo. In GemStone I can move
>> around the stack (restart, proceed, into, etc), I can inspect/explore the
>> instance variables or context variables (on the bottom part of the
>> debugger), etc. But what I cannot do is to print/inspect/do pieces of
>> random code inside the executing method. That would only work if I don't
>> refer to any temp or inst variable.
>> >
>> > So...is this a known issue? Are there workarounds?
>> >
>> > Thanks!
>> >
>> > --
>> > Mariano
>> > http://marianopeck.wordpress.com
>> > _______________________________________________
>> > Glass mailing list
>> > Glass at lists.gemtalksystems.com
>> > http://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> 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/20131217/9c652ecc/attachment.html>