Re: [ruby-gnome2-devel-en] [ANN] Ruby-GNOME2 3.0.4

[Kouhei S. <ko...@co...>]

Hi,

Thanks for your report.

In <144...@ss...>
  "Re: [ruby-gnome2-devel-en] [ANN] Ruby-GNOME2 3.0.4" on Tue, 22 Sep 2015 11:38:43 +0200,
  Stefan Salewski <ma...@ss...> wrote:

> Would be great if we can avoid the crashes in future. I will contact
> Gentoo developers again and ask to put latest ruby-gnome2 in the
> package repositories -- they already tried with 3.02 but many test
> failed and gtksourceview did not compile at all, see
> https://bugs.gentoo.org/show_bug.cgi?id=560520

Could your show build log for gtksourceview compile?

> When you are interested in testing your bindings, you may try my
> schematics editor from my homepage. Ruby peted.rb should start with an
> empty sheet, and you may draw some lines or other graphic elements.
> That tool is indeed a very heavy test for ruby-gnome -- it is not yet
> finished and contains bugs caused by me. But currently often it crashes
> with something like 
>  
> /usr/lib64/ruby/site_ruby/2.2.0/gobject-introspection/repository.rb:27:
> [BUG] Segmentation fault at 0x00000000000018
> ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux]
> 
> I think that should not occur, and have no idea how to debug/fix that.

I've fixed it at master.
Cloud you try master?
  https://github.com/ruby-gnome2/ruby-gnome2/#install-from-github-master-branch

There are some bugs in your program. If an error is raised
in callback (block registered by signal_connect), your
program will report Ruby level backtrace, C level backtrace
and so on at exit.

Normally, you should not raise any error in callback because
we can't recover from the error.


Thanks,
--
kou