barjunk
4/2/2008 7:38:00 AM
On Apr 1, 7:04 pm, barjunk <barj...@attglobal.net> wrote:
> On Mar 31, 8:46 am, barjunk <barj...@attglobal.net> wrote:
>
>
>
> > On Mar 31, 4:14 am, Chiyuan Zhang <plus...@gmail.com> wrote:
>
> > > It seems to be recursion level too deep. Have you tried to
> > > run ruby in gdb and get a backtrace when the program faulted?
> > > gdb /usr/bin/ruby test.rb
>
> > > 2008/3/31, barjunk <barj...@attglobal.net>:
>
> > > > I'm running a ruby script like so:
>
> > > > ruby test.rb
>
> > > > and because it has some problems it eventually crashes with
>
> > > > 'stack level too deep (SystemStackError)'.
>
> > > > This is a problem I'm looking into, however, if I run the program like
> > > > this:
>
> > > > rdebug test.rb
>
> > > > It doesn't crash in the same place. In fact, I haven't been able to
> > > > get it to crash at all.
>
> > > > What sort of things could cause this to take place? This happens in
> > > > 1.8.4 and the latest 1.8.6.
>
> > > > I haven't finished trying to find the reason why my ruby program
> > > > crashes in the first place, but it just seems odd that it wouldn't
> > > > also crash when using rdebug.
>
> > > > Ideas, suggestions?
>
> > > > Mike B.
>
> > Thanks. I have used gdb to trace the problem...I'm still working on
> > that. However, the curious part is that the error doesn't occur when
> > using rdebug....which is the part I'm currently trying to understand.
>
> > Mike B.
>
> Further testing shows that using rdebug still fails, it just takes a
> few more iterations before it does. It is still wierd that it would
> fail in a different spot.
>
> Mike B.
Well I never figured out why rdebug behaved differently, but after
removing all my references to rb_warn from my extension...I couldn't
get it to crash.
So for some reason I don't understand at the moment, rb_warn was
causing the errors.
Mike B.