Hi all.
When I try to use RUDL, after working around the rubygems problem, I
tried to run some of the samples. Most of them seemed to work fine,
except for the fact that they like to exit by segfaulting.
Me: "You're CLOSED!"
RUDL: "You can't close me because *I* segfault!!"
So yeah. Any clues?
--
- nornagon
I ran into some odd behavior with RUDL a while back; it sort of went
away after I added a method_missing implementation in the extension
code. Details are here:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/107693
Yours,
Tom
On Wed, 2005-08-03 at 22:06 +0900, nornagon wrote:
Hi all.
When I try to use RUDL, after working around the rubygems problem, I
tried to run some of the samples. Most of them seemed to work fine,
except for the fact that they like to exit by segfaulting.Me: "You're CLOSED!"
RUDL: "You can't close me because *I* segfault!!"So yeah. Any clues?
Hmm, that seems not to work.
I applied the patch, and:
$ ruby urlaubtris.rb
(eval):118: [BUG] Segmentation fault
ruby 1.8.2 (2004-12-25) [i686-linux]
Aborted
(I got that before the patch, too.)
And it still segfaults rather than quitting 
On 8/3/05, Tom Copeland <tom@infoether.com> wrote:
On Wed, 2005-08-03 at 22:06 +0900, nornagon wrote:
> Hi all.
>
> When I try to use RUDL, after working around the rubygems problem, I
> tried to run some of the samples. Most of them seemed to work fine,
> except for the fact that they like to exit by segfaulting.
>
> Me: "You're CLOSED!"
> RUDL: "You can't close me because *I* segfault!!"
>
> So yeah. Any clues?I ran into some odd behavior with RUDL a while back; it sort of went
away after I added a method_missing implementation in the extension
code. Details are here:http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/107693
--
- nornagon