From: Tobias Peters <t-peters@...>
Date: 2001-08-14T06:35:41+09:00
Subject: [ruby-talk:19661] Threads and their stack

In [ruby-talk:12430] I read:
: All threads are created equal (except the "main" thread), so that
: there's no such thing like parent thread.  The implementation does not
: preserve the information of the creating thread.

While threads have no knowledge of their parent thread, they actually have
access to the execution stack that led to their creation (via
kernel::caller).

I think it is feature that prevented me to recursively create threads in
an application.  All created threads exit properly and have the main
thread call join on them. Just their stack size increases with every
created thread, and ruby finally runs out of memory.

Would it be possible to modify ruby in such a way that threads can no
longer access the execution stack prior to their creation, so that it does
not occupy memory?

Do any applications already rely on that feature?

Tobias