[v8-users] Re: Building v8 shared library on windows

There are a couple of things I don't understand: -How can I use V8 with VS2019, if working DLLs can't be obtained? -Will the MSVC way ever be fixed? I cannot use precompiled DLLs if I don't know if I will be able to update them to a newer version of V8, that wouldn't be sustainable. Thank you

RE: [v8-users] Re: Building v8 shared library on windows

Oh, that’s great. Thank you. I will try to apply similar patch locally to the 7.8.279.23, since I am allowed to use only “stable” versions of V8. - Ivan From: 'Bill Ticehurst' via v8-users Sent: Friday, December 20, 2019 20:02 To:

RE: [v8-users] Re: Building v8 shared library on windows

Yes, that’s true. But fortunately, I don’t use all that stuff that has STL classes in the interface, except libplatform, so works for me, and may work for someone else. From: 'Bill Ticehurst' via v8-users Sent: Thursday, December 19, 2019 20:43 To:

[v8-users] Re: Building v8 shared library on windows

FWIW: I played around with the last night for a couple hours and got a release build working using a "component build" and MSVC. It was mostly moving some inline functions and adding some V8_EXPORT_PRIVATE statements (which effectively add the "__declspec(dllexport)" statements to expose

Re: [v8-users] Segmentation fault when disposing of an isolate.

Manually invoking the destructor )(` v8.~_V8();`) is shady, and probably the cause of the problem. It looks like a UAF when the Isolate destructor is called naturally at the end of the block. I’m not sure why it worked in earlier versions, though. Sent from my iPhone > On Dec 20, 2019, at

Re: [v8-users] Re: Segmentation fault when disposing of an isolate.

Hi Jakob thanks for the reply. Yes this issue occurs outside of Valgrind as well. When I execute the test program from the command line the output is: "2489.824" Segmentation fault (core dumped) When I use gdb: (gdb) run Starting program: /home/tom/projects/v8_workspace/testing [Thread

Re: [v8-users] Re: Segmentation fault when disposing of an isolate.

Does this happen outside of Valgrind too? Looks like the address in question was mmap'ed, so yeah, it's "not stack'd, malloc'd or (recently) free'd", but that doesn't mean it's invalid. On Fri, Dec 20, 2019 at 2:32 PM Tom Hanks wrote: > Some extra context, here is how the test program is being

[v8-users] Re: Segmentation fault when disposing of an isolate.

Some extra context, here is how the test program is being compiled: g++ testing.cxx -I v8 -I v8/include -lv8_monolith -Lv8/out.gn/x64.release.sample/obj/ -pthread -std=c++0x -ggdb -o testing -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users ---

[v8-users] Segmentation fault when disposing of an isolate.

Hi there! Full disclosure, I'm swimming in the deep end of the pool with half-deflated floaties when it comes to C and C++. I'm currently working on making v8eval (a super simple wrapper for V8) work with version 8.0.426.9 of V8. The library seems to work