Bug #2186: Fwd: Segfaults after multiple call of ruby_node_run

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: *

[yugui (Yuki Sonoda)]

=begin
Just forwarding to the redmine so that it recognizes the new issue.

---------- Forwarded message ----------
From: Christoph Kappel [e-mail]
Date: 2009/10/9
Subject: [ruby-core:26012] Segfaults after multiple call of ruby_node_run
To: ruby-core [e-mail]

Hello list,

I am just trying to solve the embedding issue (ruby-core:25927) and
tried to make a small testing program to narrow it down.
Actually I stumbled over another thing which I don't understand, why
does this program segtaults in the second run of the loop:

It's started like this: ./test test.rb

test.c

#include <stdio.h>
#include <unistd.h>
#include <ruby.h>

RUBY_GLOBAL_SETUP

int
main(int argc,
 char *argv[])
{
 void *node = NULL;

 if(2 != argc)
   {
     fprintf(stderr, "Usage: %s \n", argv[0]);
     exit(1);
   }

 ruby_sysinit(&argc, &argv);
 RUBY_INIT_STACK;
 ruby_init();

 node = ruby_options(argc, argv);

 while(1)
   {
     ruby_run_node(node);

     sleep(1);
   }

 rb_exit(0);

 return(0);
}

test.rb

puts "foobar"

--
Yuki Sonoda (Yugui)
[e-mail]
http://yugui.jp
=end

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Rejected
• ruby -v set to *

=begin
ruby_run_node() implies ruby_cleanup().
Don't call ruby_cleanup() twice or more.
Use ruby_exec_node() instead.
=end

[unexist (Christoph Kappel)]

=begin
ruby_exec_node() isn't in any of the headers in /usr/include, but it works with an implicit declaration warning of the compiler. Will this function be added in the headers too?
Also a hint in README.EXE about this behaviour with ruby_cleanup() would be nice. In the case I just overread it, my bad.
=end