[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2018-01-22 Thread jeff stein
Hello Scott - Do you know of anyone who could help on a v8 integration project? We are looking to put together a prototype to demonstrate capabilities and need help with embedding V8. Do you know anyone or are you interested possibly? Many thanks, Jeff Stein On Tuesday, June 27, 2017 at 12:

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2018-01-22 Thread jeff stein
Hello Zac - I was wondering if you could help with finding someone who could help us on a V8 integration project. Kind regards, Jeff Stein On Thursday, January 18, 2018 at 8:05:35 AM UTC-5, Zac Hansen wrote: > > quick note, if you compile something with -fsanitize=undefined, it will > create

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2018-01-18 Thread Zac Hansen
quick note, if you compile something with -fsanitize=undefined, it will create a dependency on this typeinfo because it brings in the vptr sanitizer (among a bunch of others). You can run with all the undefined sanitizers except vptr with: -fsanitize=undefined -fno-sanitize=vptr On Thursday,

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2017-07-27 Thread Zac Hansen
I link against it all the time with rtti and exceptions and don't have any problems as long as I don't let any exceptions get into the actual V8 code. Obviously you can't do anything with it that requires typeinfo on the v8 types, but it doesn't stop you from linking ALL code that uses RTTI

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2017-07-27 Thread Benjamin B.
Hello, I got the exact same problem and your answer solved it. Can you explain me a bit more in detail what magic happens ? Thank you :) On Tuesday, June 27, 2017 at 7:34:57 PM UTC+2, Scott Davies wrote: > > To (tentatively) answer my own question: V8 appears to be mostly compiled > without R

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2017-06-27 Thread Scott Davies
To (tentatively) answer my own question: V8 appears to be mostly compiled without RTTI by default, and woe unto those poor souls who compile and link against it without also adding -fno-rtti. Sigh. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users -

[v8-users] Re: Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

2017-06-27 Thread Scott Davies
Oops...never mind my final stupid question, because ninja does in fact have an obvious -v flag. :) Any other ideas about what might actually be causing the problem would still be greatly appreciated, however. On Tuesday, June 27, 2017 at 9:57:36 AM UTC-7, Scott Davies wrote: > > Hi -- > > I'm