From: Seth Kurtzberg <seth@...>
Date: 2003-03-03T03:45:02+09:00
Subject: Re: Ruby 1.8.0 bug

On Sunday 02 March 2003 11:10 am, Mauricio Fern�ndez wrote:
> On Mon, Mar 03, 2003 at 02:36:07AM +0900, Seth Kurtzberg wrote:
> > On Sunday 02 March 2003 10:22 am, Mauricio Fern�ndez wrote:
> > > On Mon, Mar 03, 2003 at 01:50:48AM +0900, Seth Kurtzberg wrote:
> > > > On Sunday 02 March 2003 09:47 am, nobu.nokada@softhome.net wrote:
> > > > > Hi,
> > > > >
> > > > > At Mon, 3 Mar 2003 01:10:01 +0900,
> > > > >
> > > > > Child wrote:
> > > > > > Sometimes in my application I get following message:
> > > > > > [BUG] unknown node type 0
> > > > > > ruby 1.8.0 (2003-02-16) [i686-linux-gnu]
> > > > > > Aborted
> > > > >
> > > > > Can you show the stack trace?
> > > >
> > > > When I see this behavior, if I show the stack trace the message no
> > > > longer occurs.  Similarly with running under the debugger.  (That's
> > > > how I found out that it seems to be caused by argument type
> > > > mismatches.)
> > >
> > > Aren't you getting a core dump?
> >
> > No, obviously not.  If I were getting a core dump I would have the stack
> > trace.
>
> You should :) If you're in bash do
>
> batsman@tux-chan:~$ ulimit -c
> 0
> batsman@tux-chan:~$ ulimit -c 20000
> batsman@tux-chan:~$ ulimit -c
> 20000
>
> Ruby will always try to dump when it exits with such an error...

I have ulimit set correctly and other apps do indeed produce cores.  I've not 
produced a core from this with Ruby 1.8.

-- 
Seth Kurtzberg
M. I. S. Corp.
480-661-1849
seth@cql.com