Re: [v8-users] Any build flag to maintain regular v8 stack trace?
It does. --gdbjit_full gives me the complete stack. Thanks again! On Wednesday, September 28, 2016 at 12:09:52 AM UTC-7, Ben Noordhuis wrote: > > On Sat, Sep 24, 2016 at 2:40 AM, Jane Chen > wrote: > > Thanks, Ben! > > > > I added that flag to my v8 init code. Now I get: > > > > 12 xdmp::JSEngine::evalBuiltin() > > /space/projects/head/xdmp/src/JSEngine.cpp:11794 0x0391466e > > 11 xdmp::JSEngine::evalBuiltin() > > /space/projects/head/xdmp/src/JSEngine.cpp:11766 0x039141ec > > 10 v8::internal::FunctionCallbackArguments::Call() > > /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 > > 9 v8::internal::(anonymous namespace)::HandleApiCallHelper() > > /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 > > 8 v8::internal::Builtin_Impl_HandleApiCall() > > /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 > > 7 v8::internal::Builtin_HandleApiCall() > > /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d > > 6 0x332193c06147 > > 5 0x332193c06081 > > 4 0x7ffad924d2a0 > > 3 0x0003 > > 2 0x7ffad924d308 > > 1 LazyCompile:~isPrime :1() 0x332193c6b884 > > > > I suppose that's as good as it gets, right? Any performance penalties > to > > leave it on always? > > I suppose so; does --gdb_jit_full make a difference? As to performance: > > 1. --gdb_jit implies --nocompact_code_space so the code space (where > generated machine code is stored) may get fragmented over time. I > have never observed that to be a problem in practice, though, even in > long-running programs. > > 2. There is some bookkeeping involved but it's not huge. Your > application may run a few percent slower, depending on what it does. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Any build flag to maintain regular v8 stack trace?
On Sat, Sep 24, 2016 at 2:40 AM, Jane Chen wrote: > Thanks, Ben! > > I added that flag to my v8 init code. Now I get: > > 12 xdmp::JSEngine::evalBuiltin() > /space/projects/head/xdmp/src/JSEngine.cpp:11794 0x0391466e > 11 xdmp::JSEngine::evalBuiltin() > /space/projects/head/xdmp/src/JSEngine.cpp:11766 0x039141ec > 10 v8::internal::FunctionCallbackArguments::Call() > /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 > 9 v8::internal::(anonymous namespace)::HandleApiCallHelper() > /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 > 8 v8::internal::Builtin_Impl_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 > 7 v8::internal::Builtin_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d > 6 0x332193c06147 > 5 0x332193c06081 > 4 0x7ffad924d2a0 > 3 0x0003 > 2 0x7ffad924d308 > 1 LazyCompile:~isPrime :1() 0x332193c6b884 > > I suppose that's as good as it gets, right? Any performance penalties to > leave it on always? I suppose so; does --gdb_jit_full make a difference? As to performance: 1. --gdb_jit implies --nocompact_code_space so the code space (where generated machine code is stored) may get fragmented over time. I have never observed that to be a problem in practice, though, even in long-running programs. 2. There is some bookkeeping involved but it's not huge. Your application may run a few percent slower, depending on what it does. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Any build flag to maintain regular v8 stack trace?
Thanks, Ben! I added that flag to my v8 init code. Now I get: 12 xdmp::JSEngine::evalBuiltin() /space/projects/head/xdmp/src/JSEngine.cpp:11794 0x0391466e 11 xdmp::JSEngine::evalBuiltin() /space/projects/head/xdmp/src/JSEngine.cpp:11766 0x039141ec 10 v8::internal::FunctionCallbackArguments::Call() /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 9 v8::internal::(anonymous namespace)::HandleApiCallHelper() /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 8 v8::internal::Builtin_Impl_HandleApiCall() /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 7 v8::internal::Builtin_HandleApiCall() /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d 6 0x332193c06147 5 0x332193c06081 4 0x7ffad924d2a0 3 0x0003 2 0x7ffad924d308 1 LazyCompile:~isPrime :1() 0x332193c6b884 I suppose that's as good as it gets, right? Any performance penalties to leave it on always? On Friday, September 23, 2016 at 11:42:08 AM UTC-7, Ben Noordhuis wrote: > > On Fri, Sep 23, 2016 at 1:10 AM, Jane Chen > wrote: > > Thanks Ben for the tip. > > > > I tried building with: > > > > make -j24 x64.debug werror=no GYPFLAGS="-Dv8_use_external_startup_data=0 > > -Dcomponent=shared_library -Dv8_enable_gdbjit=1" > > > > In my gdb-backed debugger, I still got: > > > > 28 xdmp::constructType() /space/projects/head/xdmp/src/JSEngine.cpp:2875 > > 0x038c92f3 > > 27 v8::internal::FunctionCallbackArguments::Call() > > /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 > > 26 v8::internal::(anonymous namespace)::HandleApiCallHelper() > > /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 > > 25 v8::internal::Builtin_Impl_HandleApiCall() > > /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 > > 24 v8::internal::Builtin_HandleApiCall() > > /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d > > 23 0x07bc4d206147 > > 22 0x07bc4d206081 > > 21 0x7ffad9a72d90 > > 20 0x0003 > > 19 0x7ffad9a72df8 > > 18 0x07bc4d269ead > > 17 0x3481b3104399 > > 16 0x19063552bb29 > > 15 0x3481b31cdd49 > > 14 0x3308b9f1c831 > > 13 0x19063552bb29 > > 12 0x3481b3104399 > > 11 0x190635529f49 > > 10 0x190635504201 > > 9 0x7ffad9a72e28 > > 8 0x07bc4d242403 > > 7 0x3308b9f11869 > > 6 0x190635529f49 > > 5 0x07bc4d242321 > > 4 0x000c > > 3 0x7ffad9a72e90 > > 2 0x07bc4d225a6f > > 1 0x > > > > What could I be missing? > > Mea culpa, Jane, I forgot to mention that you need to pass --gdbjit > (and optionally --gdbjit_full) to V8. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Any build flag to maintain regular v8 stack trace?
On Fri, Sep 23, 2016 at 1:10 AM, Jane Chen wrote: > Thanks Ben for the tip. > > I tried building with: > > make -j24 x64.debug werror=no GYPFLAGS="-Dv8_use_external_startup_data=0 > -Dcomponent=shared_library -Dv8_enable_gdbjit=1" > > In my gdb-backed debugger, I still got: > > 28 xdmp::constructType() /space/projects/head/xdmp/src/JSEngine.cpp:2875 > 0x038c92f3 > 27 v8::internal::FunctionCallbackArguments::Call() > /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 > 26 v8::internal::(anonymous namespace)::HandleApiCallHelper() > /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 > 25 v8::internal::Builtin_Impl_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 > 24 v8::internal::Builtin_HandleApiCall() > /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d > 23 0x07bc4d206147 > 22 0x07bc4d206081 > 21 0x7ffad9a72d90 > 20 0x0003 > 19 0x7ffad9a72df8 > 18 0x07bc4d269ead > 17 0x3481b3104399 > 16 0x19063552bb29 > 15 0x3481b31cdd49 > 14 0x3308b9f1c831 > 13 0x19063552bb29 > 12 0x3481b3104399 > 11 0x190635529f49 > 10 0x190635504201 > 9 0x7ffad9a72e28 > 8 0x07bc4d242403 > 7 0x3308b9f11869 > 6 0x190635529f49 > 5 0x07bc4d242321 > 4 0x000c > 3 0x7ffad9a72e90 > 2 0x07bc4d225a6f > 1 0x > > What could I be missing? Mea culpa, Jane, I forgot to mention that you need to pass --gdbjit (and optionally --gdbjit_full) to V8. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Any build flag to maintain regular v8 stack trace?
Thanks Ben for the tip. I tried building with: make -j24 x64.debug werror=no GYPFLAGS="-Dv8_use_external_startup_data=0 -Dcomponent=shared_library -Dv8_enable_gdbjit=1" In my gdb-backed debugger, I still got: 28 xdmp::constructType() /space/projects/head/xdmp/src/JSEngine.cpp:2875 0x038c92f3 27 v8::internal::FunctionCallbackArguments::Call() /space/projects/v8-git/v8/src/api-arguments.cc:19 0x7549cef9 26 v8::internal::(anonymous namespace)::HandleApiCallHelper() /space/projects/v8-git/v8/src/builtins.cc:5311 0x75521150 25 v8::internal::Builtin_Impl_HandleApiCall() /space/projects/v8-git/v8/src/builtins.cc:5341 0x75569d92 24 v8::internal::Builtin_HandleApiCall() /space/projects/v8-git/v8/src/builtins.cc:5329 0x75524c1d 23 0x07bc4d206147 22 0x07bc4d206081 21 0x7ffad9a72d90 20 0x0003 19 0x7ffad9a72df8 18 0x07bc4d269ead 17 0x3481b3104399 16 0x19063552bb29 15 0x3481b31cdd49 14 0x3308b9f1c831 13 0x19063552bb29 12 0x3481b3104399 11 0x190635529f49 10 0x190635504201 9 0x7ffad9a72e28 8 0x07bc4d242403 7 0x3308b9f11869 6 0x190635529f49 5 0x07bc4d242321 4 0x000c 3 0x7ffad9a72e90 2 0x07bc4d225a6f 1 0x What could I be missing? On Wednesday, September 21, 2016 at 11:26:24 PM UTC-7, Ben Noordhuis wrote: > > On Thu, Sep 22, 2016 at 2:41 AM, Jane Chen > wrote: > > Embedding v8. Currently on 4.6.88, and in the process of upgrading to > > 5.3.lkgr. > > > > When I do a pstack of my program embedding v8, some of the v8 frames > show up > > as ???. I wonder whether there's a build flag I could use to enable the > > full stack trace of v8 frames. > > > > Please advise. > > > > Thanks. > > If your pstack is a wrapper around gdb, compile V8 with > v8_enable_gdbjit set to 1 (`make native gdbjit=on`) and it should be > able to decode JS stack frames. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Any build flag to maintain regular v8 stack trace?
On Thu, Sep 22, 2016 at 2:41 AM, Jane Chen wrote: > Embedding v8. Currently on 4.6.88, and in the process of upgrading to > 5.3.lkgr. > > When I do a pstack of my program embedding v8, some of the v8 frames show up > as ???. I wonder whether there's a build flag I could use to enable the > full stack trace of v8 frames. > > Please advise. > > Thanks. If your pstack is a wrapper around gdb, compile V8 with v8_enable_gdbjit set to 1 (`make native gdbjit=on`) and it should be able to decode JS stack frames. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Any build flag to maintain regular v8 stack trace?
Embedding v8. Currently on 4.6.88, and in the process of upgrading to 5.3.lkgr. When I do a pstack of my program embedding v8, some of the v8 frames show up as ???. I wonder whether there's a build flag I could use to enable the full stack trace of v8 frames. Please advise. Thanks. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
