-
Notifications
You must be signed in to change notification settings - Fork 123
SEGFAULT in v8::internal::FixedArrayBase::length when calling V8::C::Object::New() #156
Comments
Here's how this looks from Ruby's point of view: https://gist.github.com/ignisf/f2bf6ca540938c1a8072 |
This might not be an ARM-specific issue, see rubyjs/therubyracer#310 |
Same issue under a Debian Daily image on an x86 system:
|
@cowboyd, we need somebody more knowledgeable in debugging C++ to handle this one |
Also verified on Debian 7 x86 and x86_64. This seems to be happening when an object is created without a This segfault is also happening in therubyracer's specs due to a monkey patch that doesn't work anymore (rubyjs/therubyracer#333). To be clear, IMO this is just an erroneous way of creating an object and not an actual bug. Unless you count the no-error-message crash as bug, which I agree with, but should not be an issue for this project. Working test: require 'v8'
V8::C::HandleScope() do
template = V8::C::ObjectTemplate.New()
context = V8::C::Context.New(nil, template)
context.Enter
p V8::C::Object.New()
end |
awesome! |
This issue arises on ARMv7.
Test:
Backtrace:
The text was updated successfully, but these errors were encountered: