At 08:43 AM 3/22/2002 -0500, Bryan C. Warnock wrote:
>On Friday 22 March 2002 08:22, Clinton A. Pierce wrote:
> > Some patches committed last evening nearly took care of the problem -- at
> > least they appeared to make my small example appear to
> > work. Sometimes. :) Here's a slightly larger but better example that so
> > far hasn't failed to show the stack corruption problem anywhere:
>
>Here's my output:
>
>Whammo 26> parrot clint2.pbc
>one<-- save ( ;boundary)
>two<-- save ( ;boundary)
>three<-- save ( ;boundary)
>four<-- save ( ;boundary)
>five<-- save ( ;boundary)
>six<-- save ( ;boundary)
>seven<-- save ( ;boundary)
>eight<-- save ( ;boundary)
>nine<-- save ( ;boundary)
>ten<-- save ( ;boundary)
>eleven<--saved (endproc)
No no. That's always fine. Now dump the stack. That's where the joy is!
Stack Dump: (top to bottom)
0 Str eleven
1 Str ten
2 Str nine
3 Str eight
4 Str seven
5 Str six
6 Str five
7 Str n
8 Str
9 Str e
10 Str ;
