From: Tanaka Akira <akr@...17n.org>
Date: 2004-12-16T11:42:22+09:00
Subject: Re: [BUG] unknown node type 0 - SERIOUS ENOUGH TO MIGRATE AWAY FROM RUBY?

In article <1103155193.940450.14567.nullmailer@x31.priv.netlab.jp>,
  Yukihiro Matsumoto <matz@ruby-lang.org> writes:

> Because it's often caused by GC invoked at certain timing, even mere
> spaces or newlines can change the situation.

I have some idea to ease debugging such bugs.

1. "always GC" option
  It makes easier to modify script without lose a problem.

  However it makes ruby drastically slow, it should take an optional
  argument N which means "always GC after N GC opportunities".

2. record last GC backtrace.
  It shows GC timing which we hard to see now.
  
  It is not difficult with gcc if __builtin_return_address(level) and
  __builtin_frame_address(level) works well where level > 0.
-- 
Tanaka Akira