From: Iain Dooley <idoo4002@...>
Date: 2005-08-29T22:09:50+09:00
Subject: Re: catching segmentation faults from Ruby



ts wrote:
>>>>>>"I" == Iain Dooley <idoo4002@mail.usyd.edu.au> writes:
> 
> 
> I> this is part of Qt/Ruby bindings, so obviously what's happening is that, 
> I> because @parent.child("someName") returns nil, trying to access this is 
> I> causing a segmentation fault. so @parent.child("someName").text is 
> I> trying to call a function on an object that doesn't exist.
> 
>  It must not segfault
> 
> moulon% ruby -e 'nil.text'
> -e:1: undefined method `text' for nil:NilClass (NoMethodError)
> moulon% 
> 
> I> does that sound like it is a bug in Qt Ruby bindings?
> 
>  try to reproduce it outside your embedded applications, if it segfault the
>  bug is in Qt ruby

okay, thanks for your help.

iain