When debugging D8 with GDB (gdbjit enabled) major parts of the backtrace are still marked with ??.
#0 0x0000000001eab2ef in StringMark::StringMark (this=0x7fffffffdc48, other=...) at ../src/mark.cc:214 #1 0x0000000001e80799 in v8::internal::__RT_impl_Runtime_StringIsMarked (args=..., isolate=0x27b5530) at ../src/runtime/runtime-strings.cc:107 #2 0x0000000001e80514 in v8::internal::Runtime_StringIsMarked (args_length=1, args_object=0x7fffffffdd28, isolate=0x27b5530) at ../src/runtime/runtime-strings.cc:102 #3 0x00003b15c7e84204 in ?? () #4 0x00003b15c7e84141 in ?? () #5 0x00007fffffffdd00 in ?? () #6 0x0000000000000006 in ?? () #7 0x00007fffffffdd40 in ?? () ... The statement executed via D8 is String.fromCharCode(100).isMarked() I know that V8 crashes because of accessing an uninitialized pointer in the isMarked() call, but what I would like to know is what happens all the way before on the fromCharCode(100) call. Any tips on how to debug this properly? Thanks & best regards, Patrick -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" 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.
