PR# 16849 Qualified anchored type that references expanded feature uses huge amount of stack

This example is similar to bug #16848 and may be due to the same cause.
A qualified anchored type that references a feature of an expanded type
causes system execution to use an enormous amount of stack space
(more than 1.7 GB) when system is melted.  If stacksize is unlimited, system 
execution works correctly but uses a huge amount of stack space.  If
stacksize is limited via:

   limit stacksize 1700000

then execution of a melted system ends with a seg fault, presumably due to
running out of stack space.  Frozen code executes quickly and correctly
when stack size is limited to 16 KB.

I didn't add an eweasel test because I couldn't figure out a good way to
show that system execution was using a huge amount of stack.

Melt with attached classes and config file.
Limit stacksize via:

   limit stacksize 1000000

which is about 1 GB.
Execute system.  Crashes with seg fault.
Now make stack size unlimited via:

   limit stacksize unlimited

Execute system.  Execution eventually finishes on my machine, which
has 2 GB of physical memory, but there is a lot of disk activity and execution
takes more than 1 minute to complete.

I believe this was the same as bug #16848.  The blowup in
stack size does not occur with rev 83602 (but does occur
with rev 83355).  Tested on Solaris x64.

I can't think of any way to automate this.
Closing report.

Attachments for problem report #16849