On 14.07.2024 11:31, Rick McGuire wrote:
On Sun, Jul 14, 2024 at 5:28 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
On 13.07.2024 17:31, Rick McGuire wrote:
That makes absolutely no sense. Once the new activity is started, there is
no guarantee that
the stackframe or even the activity from which it was spawned even exists
any more. The
original activity has continued on doing its own stuff.
A question here: I thought that if storing Rexx objects in a Rexx
collection they are pinned
and do not get garbage collected.
The stack frame object would not be garbage collected, but the stack frame itself and the things
that it referred to would no longer exist or be valid.
Thank you!
Will make the TraceObject StackFrame entry pointing to a StringTable entry instead that contains
.nil or string values only for the stack frame entries at the point the traceObject gets created.
This way no unexpected crashes can occur if accessing the entries at a later time when the activity
and the stackframe are not available anymore.
Still the trace related information which package, line, traceline, type etc. will remain available.
The referrals to executable or object will get replaced by their identity hash values such that post
anaylsis of trace log objects allows to determine the identity later which may be interesting e.g.
for analyzing message communication patterns and the like.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
