开发者

Any known causes for "illegal hardware instruction rails server" errors in Rails 3.1 RC?

开发者 https://www.devze.com 2023-03-08 09:16 出处:网络
I\'m not sure what\'s causing this error - and am not sure how to debug the issue.Does anyone have any pointers for advice on the error \"illegal hardware instructionrails server\" when running a Rail

I'm not sure what's causing this error - and am not sure how to debug the issue. Does anyone have any pointers for advice on the error "illegal hardware instruction rails server" when running a Rails 3.1 app?

thanks in advance, dan

UPDATE:

The error is always reproducible and only occurs in a project I'm trying to upgrade from Rails 3.0 to Rails 3.1 (RC1)

I didn't see anything in the logs - except for a bunch of warnings:

DEPRECATION WARNING: class_inheritable_attribute is deprecated, please use class_attribute method instead. Notice their behavior are slightly different, so refer to class_attribute documentation first. (called from <class:Entity> at .../app/models/entity.rb:3)

The w开发者_StackOverflow中文版arnings are from the use of a gem called acts_as_audited. If I comment that out... it works. I didn't think a warning would cause a rails to report a hardware error.


Got the same error, but I've solved it. My problem was caused by a v8 engine installed from HomeBrew. Simply remove it solves the issue.

Your situation may be different, I offer you a good way to inspect it. When your rails server crashed, Mac OS X will save a crash report as

~/Library/Logs/DiagnosticReports/ruby_*.crash

Then you can check this file, and find the crashed thread descriptions. On my system, it reports:

Thread 4 Crashed: 0 libv8.dylib 0x00000001030a08f8 v8::internal::HandleScope::DeleteExtensions(v8::internal::Isolate*) + 24


Is the error reproducible? If yes, then you may suspect the software. Maybe some library or ruby itself has been recently upgraded?

In any case it would be a good idea to check the machine against memory errors and disk problems. Maybe there is some info in the system logs?

You haven't said what system you are on, but in any case - ensure the hardware is OK, ensure the basic system is OK, check whether your code has no infinite loops or similar errors, check whether the error still exists on different versions of Rails or ruby.

That's for start. :)

0

精彩评论

暂无评论...
验证码 换一张
取 消