Re: [v8-users] Re: Significant JSON::Stringify, Uint8Array, or ArrayBuffer changes between v5.4 to v6.0.186

Thanks Jakob. Sorry, I'm not sure how to assign issues, but here's the link: https://bugs.chromium.org/p/v8/issues/detail?id=6533 On Tuesday, June 27, 2017 at 12:39:44 AM UTC-7, Jakob Gruber wrote: > > Interesting. It'd be very helpful if you could open a bug at > crbug.com/v8/new with a full

Re: [v8-users] How to compile V8 without libplatform?

On Tue, Jun 27, 2017 at 9:28 PM, Lucian Caetano wrote: > Hello, I would like to know how to compile V8 without libplatform, as I > would like to implement my own event loop and my message queue, but when I > do not initialize the platform I get a segmentation

[v8-users] How to compile V8 without libplatform?

Hello, I would like to know how to compile V8 without libplatform, as I would like to implement my own event loop and my message queue, but when I do not initialize the platform I get a segmentation fault. -- -- v8-users mailing list v8-users@googlegroups.com

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

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] Strange link errors involving ArrayBuffer::Allocator (occur with v8 6.1, but did not occur with v8 5.5)

Hi -- I'm working on a C++ library that was compiling and linking just fine with v8 until I upgraded to a new Mac (OS 10.12.5, clang++ version 802.0.42) and moved up to the latest version of v8 (6.1.0). Now I'm getting lots of link errors involving v8::ArrayBuffer::Allocator. I've reproduced

Re: [v8-users] debugging protocol

Though F5 does not do anything but if I sever the ws connection (close chrome) and reconnect the console does not work anymore (I cannot evaluate anything on it). I worked it around by sending {"id":0,"method":"Runtime.disable"} to V8 when the ws server detects disconnection. When CDT

Re: [v8-users] Re: Significant JSON::Stringify, Uint8Array, or ArrayBuffer changes between v5.4 to v6.0.186

Interesting. It'd be very helpful if you could open a bug at crbug.com/v8/new with a full code example (including build instructions if it includes C++) and instructions to reproduce the issue. Feel free to assign it to me (jgru...@chromium.org) and I'll have a look. On Mon, Jun 26, 2017 at 6:44