I'm trying to build V8 for both X64 and ARM64 (by cross compiling). Both
builds seem to run and complete without errors, but libv8.a, libplatform.a,
etc. are not generated for either build. However, other static libraries
are successfully built (e.g. libgmock.a).
Build machine is X64 running
Thanks for tracking this down. In general, if you're willing / able to
provide a repro case, we're happy to investigate suchs bugs ourselves, so
you don't have to go through the trouble of bisecting this..
On Sun, Sep 25, 2016 at 6:06 PM PhistucK wrote:
> After bisecting,
Yes, but I could not provide a reproduction case. :(
At least not without approvals from managers, I guess.
Do you happen to know when the next stable patch release is planned (that
includes the change)? I had to instruct the test teams to use
--js-flags="--no-crankshaft" for now, which is not
I want to be able to debug the code running in my program, and in a
previous thread, I was informed that there is currently no way to do this
with over the network.
Someone mentioned that this will be (re)added eventually, but when I asked
for an estimate of a half-year that might happen, I
CompileFunctionInContext is equivalent to using with (context_extension) {
} around your function which is different from pretending it was inside
some other function.
As for the odd line numbers, can you provide a complete repro case?
On Sat, Sep 24, 2016 at 1:12 PM Zac Hansen
Hi Ben,
It turned out to be memory leak in my C++ wrapper on top of V8 - fixed it.
Thanks for the suggestion around using v8::HeapProfiler::TakeHeapSnapshot().
> On 24-Sep-2016, at 00:08, Ben Noordhuis wrote:
>
> On Fri, Sep 23, 2016 at 12:54 PM, Abhishek Singh
>