[gambit-list] How introspect frame objects

Mikael mikael.rcv at gmail.com
Thu Jun 20 10:13:48 EDT 2013


Aha got it:

For a frame object,

(##frame o) => #t

(##subprocedure-parent-name (##frame-ret o)) => the name of the procedure
that the frame regards e.g. ##read-u8

(##frame-ref o N) where N = 0 .. (##frame-fs o) - 1 => the frame's bound
objects, (##frame-slot-live? o N) checks the respective slot for aliveness.


2013/6/20 Mikael <mikael.rcv at gmail.com>

> Dear Marc,
>
> In memory leak hunting I've gotten to a place where there's two stack
> frame objects that keep the leaking pointer.
>
> How can I introspect #<frame #[number]> objects to understand where in the
> sourcecode they come from in terms of location, code content and variable
> content?
>
> Thanks,
> Mikael
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20130620/083329c8/attachment.htm>


More information about the Gambit-list mailing list