Segmentation fault in hpricot?

I have a ruby script producing this error on Ubunutu Linux amd64 (I used the
standard ubuntu ruby packages to install ruby... I got ruby gems from source
and used gem install to get mechanize). The script works fine on i386... I'm
using mechanize with threads. I can provide more info. Who should I contact?

I suppose I should compile ruby from source and see if I still get the error...
I'll try that later tonight.

ruby 1.8.4 (2005-12-24) [x86_64-linux]

/usr/lib/ruby/gems/1.8/gems/hpricot-0.4/lib/hpricot/traverse.rb:344: [BUG]
Segmentation fault

Quoting Brad Tilley <rtilley@vt.edu>:

ruby 1.8.4 (2005-12-24) [x86_64-linux]

/usr/lib/ruby/gems/1.8/gems/hpricot-0.4/lib/hpricot/traverse.rb:344: [BUG]
Segmentation fault

Sometimes, this error is produced:

/usr/lib/ruby/gems/1.8/gems/hpricot-0.4/lib/hpricot/tag.rb:32: [BUG]
rb_gc_mark(): unknown data type 0x38(0x59d240) non object

Similar problems have been brought up on 32-bit Ubuntu[1] with 1.8.4. The fellow
moved to 1.8.5 and had no further problems. Some garbage pointer is finding its
way into an object.

All bugs should be reported to the Hpricot site[2], which accepts your Rubyforge
account quite handily, and I will walk you through getting a trace with gdb.

_why

[1] http://code.whytheluckystiff.net/hpricot/ticket/21
[2] http://code.whytheluckystiff.net/hpricot

···

On Thu, Nov 23, 2006 at 08:37:36AM +0900, Brad Tilley wrote:

Quoting Brad Tilley <rtilley@vt.edu>:

> ruby 1.8.4 (2005-12-24) [x86_64-linux]
>
> /usr/lib/ruby/gems/1.8/gems/hpricot-0.4/lib/hpricot/traverse.rb:344: [BUG]
> Segmentation fault

Sometimes, this error is produced:

/usr/lib/ruby/gems/1.8/gems/hpricot-0.4/lib/hpricot/tag.rb:32: [BUG]
rb_gc_mark(): unknown data type 0x38(0x59d240) non object

_why, how do you get Trac to recognize people's RubyForge accounts?

That's spiffy!

···

On 11/22/06, _why <why@ruby-lang.org> wrote:

All bugs should be reported to the Hpricot site[2], which accepts your Rubyforge
account quite handily, and I will walk you through getting a trace with gdb.