Re: [v8-dev] Undefined backtraces when debugging with D8 and GDB JIT enabled

Thank you! The additional --gdbjit_full flag did the trick (just stumbled upon the high start up time of v8 using this flag). GDB macros provided by the tools/gdbinit file were also very helpful. On Tuesday, August 1, 2017 at 12:10:34 PM UTC+2, Ben Noordhuis wrote: > > On Mon, Jul 31, 2017 at

Re: [v8-dev] Undefined backtraces when debugging with D8 and GDB JIT enabled

On Mon, Jul 31, 2017 at 10:59 AM, Patrick Spiegel wrote: > When debugging D8 with GDB (gdbjit enabled) major parts of the backtrace are > still marked with ??. > > #0 0x01eab2ef in StringMark::StringMark (this=0x7fffdc48, > other=...) at ../src/mark.cc:214

Re: [v8-dev] Undefined backtraces when debugging with D8 and GDB JIT enabled

The tools/gdbinit file contains a couple of gdb macros that are useful here. In particular, 'jst' will print the current JS stack trace. But this will only give you JS frames. If you want to dive even deeper, you can print the code objects currently on the stack with 'jco'. Note that on x64, you

[v8-dev] Undefined backtraces when debugging with D8 and GDB JIT enabled

When debugging D8 with GDB (gdbjit enabled) major parts of the backtrace are still marked with ??. #0 0x01eab2ef in StringMark::StringMark (this=0x7fffdc48, other=...) at ../src/mark.cc:214 #1 0x01e80799 in v8::internal::__RT_impl_Runtime_StringIsMarked (args=...,