Re: [v8-users] Possible reasons of Runtime_StackGuard

2019-03-13 Thread Jakob Kummerow
To get debug symbols, you need a Debug build of V8 (or at least a Release build with symbols). You can compile one yourself, see https://v8.dev/docs/build-gn. If possible, recreating the situation in a desktop application will probably make debugging easier -- but I realize that for debugging a la

Re: [v8-users] Possible reasons of Runtime_StackGuard

2019-03-13 Thread Alexey Shcherbyna
Hi Jacob, thank you for response. I understood the main error because I tried to use libv8-nosnapshot from old v8 version. I use v8 7.2.504, I have removed old no snapshot and added libv8_external_snapshot from this repository https://github.com/NativeScript/android-runtime https://github.com

Re: [v8-users] Possible reasons of Runtime_StackGuard

2019-03-04 Thread Jakob Kummerow
Runtime_StackGuard is the mechanism by which execution of (interpreted or optimized) JavaScript code is interrupted by C++ code. From the next few stack frames you can deduce the reason an interruption was requested: generated code had performed enough allocations that it was time to do a round of