Forum: Ruby on Rails -517611318:Fixnum ... WTF?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2006-01-19 02:09
(Received via mailing list)
I'm getting occasional errors that look like:

Some method called for -517611318:Fixnum

The method is constantly changing, and this error happens on ~5% of
the page loads on my Mac Tiger development box.  It's happening on
Ruby 1.8.2, and 1.8.4 compiled from source.  I haven't seen it on my
Linux production boxes.  I was wondering if anyone had seen this
before?

--
Kyle Maxwell
Chief Technologist
E Factor Media // FN Interactive
kyle@efactormedia.com
1-866-263-3261
D25d7166e80639478ef1811788b8e61e?d=identicon&s=25 Bruno Mattarollo (Guest)
on 2006-01-19 02:12
(Received via mailing list)
Yes, I've seen that when doing many many operations per second on a
"development" instance. When I change it to "production" it goes away.
I haven't really had time to track this down, so when I am loading the
data for my dev instance, I usually change the ENV to "production",
dump and reload the data from the DB and then start over in
"development" ... Not very smart but works for me :-)

/B

On 19/01/06, Kyle Maxwell <kyle@kylemaxwell.com> wrote:
> --
>
>
>


--
Bruno Mattarollo <bruno.mattarollo@gmail.com>
Currently in: Sydney, Australia
6c27f78ab0eee78732ae54e8b8718b84?d=identicon&s=25 David Felstead (Guest)
on 2006-01-19 02:46
(Received via mailing list)
Apparently this can happen if you've compiled ruby using GCC 4.0.  Run
'gcc_select 3.3' and recompile/reinstall, it should remove the
problem.  Don't forget to run 'gcc_select 4.0' afterwards though!

Cheers,

-DF
58479f76374a3ba3c69b9804163f39f4?d=identicon&s=25 Eric Hodel (Guest)
on 2006-01-19 22:11
(Received via mailing list)
On Jan 18, 2006, at 5:07 PM, David Felstead wrote:

> Apparently this can happen if you've compiled ruby using GCC 4.0.  Run
> 'gcc_select 3.3' and recompile/reinstall, it should remove the
> problem.  Don't forget to run 'gcc_select 4.0' afterwards though!

This is not a guaranteed fix, GCC 4 just makes the problem more easy
to encounter.  See the ruby-core archives.

Also note you may have linking problems with libraries built using a
different version of GCC.

--
Eric Hodel - drbrain@segment7.net - http://segment7.net
This implementation is HODEL-HASH-9600 compliant

http://trackmap.robotcoop.com
This topic is locked and can not be replied to.