While analyzing various invocation types and the caller's stack frame (for invocation entries to
allow identifying the caller from a trace log later), everything seems to work out nicely.
There is one case where the caller's stack frame cannot be generated, it seems to have to do with
methods that get run asynchroneously, e.g.:
...
o=.clz~new
o~m1 -- caller's stack frame can be built for ">I> Method "M1" with scope
..."
o~start("m1") -- caller's stack frame can NOT be built for ">I> Method "M1"
with scope ..."
...
The activity for the asynchronous message has Activity::activationFrames as NULL, such that it
cannot be used for creating a parent stack frame.
Would it possible to supply an Activity::activationFrames for asynchronous
dispatch?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
