Trouble with SIGINT signal handling after calling ruby_init() in a C++ program

Question

I'm currently working on a C++ program that embeds the Ruby interpreter using ruby_init(). However, I've noticed that after calling ruby_init(), the SIGINT (Ctrl+C) signal doesn't seem to work as expected within my program.

When Ctrl+C is pressed, the application does not close. It's only when I call ruby_finalize() that the SIGINT signal starts working again, and the application closes when Ctrl+C is pressed.

Here's a simplified version of my code:

#include <ruby.h>
#include <iostream>

int main()
{
  // SIGINT signal works at this point

  // Initialize the Ruby interpreter
  ruby_init();

  // SIGINT signal stops working after this point

  while (isOpen) {
    // Code that interacts with Ruby
  }

  // Close the Ruby interpreter
  ruby_finalize();

  // SIGINT starts working again

  return 0;
}

I'm trying to understand why the SIGINT signal is not being captured and handled correctly when Ruby is embedded. Any insights into what might be causing this behavior and how to address it would be greatly appreciated.

Thanks in advance for your assistance!

Edit:

I've attempted to capture the signal within the Ruby interpreter, but it's not receiving the interrupt signal. I've tried the following:

rb_eval_string("Signal.trap('INT') { puts 'interrupt signal received' }");