You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I plan to start working on this next week, so we'll be prepared when V8 6.7 land on v10.0.0.
I don't think v8dbg_class_SharedFunctionInfo__function_data__Object will impact llnode. I couldn't find any call to SharedFunctionInfo::GetCode... v8dbg_class_SharedFunctionInfo__name_or_scope_info__Object will be fun though 😅
Activity
mmarchini commentedon May 3, 2018
I plan to start working on this next week, so we'll be prepared when V8 6.7 land on v10.0.0.
I don't think
v8dbg_class_SharedFunctionInfo__function_data__Objectwill impact llnode. I couldn't find any call toSharedFunctionInfo::GetCode...v8dbg_class_SharedFunctionInfo__name_or_scope_info__Objectwill be fun though 😅cjihrig commentedon May 3, 2018
When I originally created the postmortem metadata test, I added the constants from llnode and mdb_v8, so it could be an mdb_v8 thing.
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7
src: fix backtrace for V8 6.7