[v8-users] Segfault calling v8::Persistent::Reset.

Embedding v8 5.3. Seeing a segfault in our stress test: Critical: #6 0x7fbf3f6c0173 in v8::internal::GlobalHandles::Node::Release() () from lib/libv8.so This happens when v8::Persistent::Reset is called. Has anyone else seen this? Any clues on what might be wrong? Thanks. -- --

Re: [v8-users] [novice] SIGSEGV upon entering new top of the stack context

On Thu, Dec 1, 2016 at 9:55 PM, Thomas Barusseau wrote: > I read somewhere that if Isolate::GetCurrent() returned NULL, it was > because the current isolate was being already used, I guess by the running > node.js itself? Node.js never unlocks the isolate while running

Re: [v8-users] [novice] SIGSEGV upon entering new top of the stack context

Hello, That makes sense, and I was pretty sure that just creating a new isolate was clearly not the way to go. Since I'm dealing with Persistent objects, what should I do, then? I read somewhere that if Isolate::GetCurrent() returned NULL, it was because the current isolate was being already

[v8-users] Re: Missing symbol ___asan_version_mismatch_check_v8

That didn't work. V8 insisted on linking with the asan runtime included with it's special version of clang, so mkpeephole wouldn't run because it couldn't find ___asan_version_mismatch_check_apple_800. I'm going to try playing with the executable path. -- -- v8-users mailing list

[v8-users] Re: Missing symbol ___asan_version_mismatch_check_v8

Well, I looked a little more closely at the compiler options and discovered that my library is not, in fact, getting compiled with ASAN. Only V8 is. Now the problem is that if I compile the library with the same compiler as V8, it can't find @executable_path/libclang_rt.asan_osx_dynamic.dylib,

[v8-users] Re: Missing symbol ___asan_version_mismatch_check_v8

I just tried compiling my library with the same prebuilt compiler used for v8 (third_party/llvm-build/Release+Asserts/bin/clang), and it still didn't work. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you

[v8-users] Re: Missing symbol ___asan_version_mismatch_check_v8

Also, d8 loads fine. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email

[v8-users] Missing symbol ___asan_version_mismatch_check_v8

I'm trying to build both V8 and my library that embeds with the address sanitizer, and I'm getting this error when trying to load my library: dlopen(v8py.so, 2): Symbol not found: ___asan_version_mismatch_check_v8 Referenced from: v8py.so Expected in: flat namespace in v8py.so What's going

[v8-users] Re: [novice] SIGSEGV upon entering new top of the stack context

I don't know the exact answer ottomh, but make sure you're running against a debug build - the error messages are a little better. Also, maybe try putting a handlescope before th eline that's crashing? --Zac On Thursday, December 1, 2016 at 8:09:01 AM UTC-8, Thomas Barusseau wrote: > > Hello,

[v8-users] [novice] SIGSEGV upon entering new top of the stack context

Hello, I'm having a hard time making this piece of code work. Basically, I need to take a node.js function (in this case : `process.emit()`), store it in a C++ class, and use it at runtime whenever a callback method is called. Here is the code :