Hello! Deepak Subramanian <[email protected]> writes:
> Please let me know the best way to debug v8 with gdb. debugging d8 is not
> helping much.
We do run d8 under GDB in order to debug V8. You will have to build V8
with debugging information, though. There are also a couple of build
options which will add some additional debugging support into V8. This
is the command I use for building:
make -j4 console=readline disassembler=on objectprint=on \
verifyheap=on backtrace=on verifypredictable=on \
gdbjit=off deprecationwarnings=on extrachecks=on \
slowdchecks=on x64.debug
Once you have a debug build of V8, it will be much easier to debug it
using GDB; run it with:
gdb --args ./out/x64.debug/d8
You can source the “tools/gdbinit“, and “tools/gdb-v8-support.py”
scripts in GDB to have some additional debugging commands loaded, for
example, you can use the “job” command to print JavaScript objects — do
check the files to learn more about the rest of commands, they come with
brief descriptions :)
Cheers,
--
⌨ Adrian
--
--
v8-users mailing list
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
