8/new, include the repro, and I will try to have
> a look next week.
>
>
>>
>> On Thursday, July 18, 2019 at 8:43:42 AM UTC-4, Jakob Gruber wrote:
>>>
>>> On Thu, Jul 18, 2019 at 2:32 PM Christopher Nelson
>>> wrote:
>>>
>>>>
way to get that to work on v8 without hacking the v8 build system.
I will perform some more tests on macOS to be sure this fixes the problem,
but so far it looks good...
On Thursday, July 18, 2019 at 9:52:49 AM UTC-4, Jakob Gruber wrote:
>
>
> On Thu, Jul 18, 2019 at 3:10 PM Christopher
is at fault
here. It happens deep inside the isolate initialization.
On Thursday, July 18, 2019 at 8:43:42 AM UTC-4, Jakob Gruber wrote:
>
> On Thu, Jul 18, 2019 at 2:32 PM Christopher Nelson > wrote:
>
>> I'm not using the same exact libc++, no. I don't have a problem doi
on how to tell V8
which libc++ to use I will very happily implement that.
On Thursday, July 18, 2019 at 1:22:04 AM UTC-4, Jakob Gruber wrote:
>
> On Wed, Jul 17, 2019 at 5:48 PM Christopher Nelson > wrote:
>
>> Thank you so much for the help that has been provided so far. Sadl
Thank you so much for the help that has been provided so far. Sadly, I
tried both of these suggestions without success.
First, I removed all of the build arguments except:
is_debug = true
target_cpu = "x64"
v8_monolithic = true
v8_enable_i18n_support = false
I built this with much the same res
ks like allocation of the new string here
>>> <https://cs.chromium.org/chromium/src/v8/src/interpreter/interpreter.cc?l=277&rcl=5bf6b8221240ae424bb2b19713bec7534125b9c5>
>>> is failing. That code has been there since 71 though.
>>>
>>> On Mon, Jul 15,
appreciated!
On Friday, July 12, 2019 at 4:54:39 PM UTC-4, Christopher Nelson wrote:
>
>
> I have the following code, which works fine on v8 7.2:
>
> isolate::isolate() {
> create_params.arra
I have the following code, which works fine on v8 7.2:
isolate::isolate() {
create_params.array_buffer_allocator =
v8::
ArrayBuffer::Allocator::NewDefaultAllocator();
