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::
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/JSEng
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::Funct
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::constructT
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
0x0
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
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.
--