1.8.3 segfaulting, how to report bugs?

ruby-talk
1

I have a large ruby program that runs fine in older versions but causes
1.8.3 to segfault (always). How and where should bugs be reported? I
searched ruby-lang.org to no avail.

I would gladly supply a copy of the program to any ruby developer for
testing, but I don't want to publicly distribute it yet.

2

I have a large ruby program that runs fine in older versions but
causes 1.8.3 to segfault (always). How and where should bugs be
reported? I searched ruby-lang.org to no avail.

I had this issue too and it was solved by appending an empty
line or a line with a comment to one of the script files.

I would gladly supply a copy of the program to any ruby developer
for testing, but I don't want to publicly distribute it yet.

The bugtracker for Ruby is available under:
http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse

Regargs,
  Stefan

···

On Saturday 01 October 2005 22:56, Joshua Swink wrote:

3

I have a large ruby program that runs fine in older versions but causes
1.8.3 to segfault (always). How and where should bugs be reported? I
searched ruby-lang.org to no avail.

If you have compiled ruby from the source and you have a version of
bison < 2.0 (bison --version) then remove the file parse.c and re-compile
ruby.

Guy Decoux

4

Stefan Lang wrote:

···

On Saturday 01 October 2005 22:56, Joshua Swink wrote:
> I have a large ruby program that runs fine in older versions but
> causes 1.8.3 to segfault (always). How and where should bugs be
> reported? I searched ruby-lang.org to no avail.

I had this issue too and it was solved by appending an empty
line or a line with a comment to one of the script files.

Thanks. I tried adding a blank line or a comment to every file,
but it still crashes. Sticking with 1.8.2 for now.