At 4:52 PM -0500 3/15/02, Clinton A. Pierce wrote:
>At 04:28 PM 3/15/2002 -0500, Dan Sugalski wrote:
>>At 4:01 PM -0500 3/15/02, Clinton A. Pierce wrote:
>>>I'm in the midst of writing some routines to debug pasm code, and
>>>one of the things I dearly want is a "stack dump" routine. I can
>>>*
At 04:28 PM 3/15/2002 -0500, Dan Sugalski wrote:
>At 4:01 PM -0500 3/15/02, Clinton A. Pierce wrote:
>>I'm in the midst of writing some routines to debug pasm code, and one of
>>the things I dearly want is a "stack dump" routine. I can *almost* code
>>this in pasm, except I'm missing one last c
At 4:01 PM -0500 3/15/02, Clinton A. Pierce wrote:
>I'm in the midst of writing some routines to debug pasm code, and
>one of the things I dearly want is a "stack dump" routine. I can
>*almost* code this in pasm, except I'm missing one last component: a
>way to tell the depth of the stack with
I'm in the midst of writing some routines to debug pasm code, and one of
the things I dearly want is a "stack dump" routine. I can *almost* code
this in pasm, except I'm missing one last component: a way to tell the
depth of the stack without causing the runtime to bail.
Any of the following
