This is indeed the correct mailing list for this question. To my knowledge we don't actually provide any hints to crashpad, and it actually makes sense that we do. We've discussed this in the past but it never became urgent. I'd love to see contributions!
Adding Ulan and Jakob because they might have some ideas on what to include. Cheers, Yang On Thu, 31 Jan 2019, 17:46 irinayat via v8-dev <[email protected] wrote: > Hello! > I am investigating postmortem debugging of V8 using the dumps collected by > Crashpad on Windows. Stepping through > crashpad::internal::ModuleSnapshotWin::GetCrashpadExtraMemoryRanges for > the binary that links in v8 code doesn't yield any additional memory ranges: > > 1:141> dx -id 0,1 -r1 > (*((crashpad::process_types::CrashpadInfo<crashpad::process_types::internal::Traits64> > *)0x69085ff000)) > > (*((crashpad::process_types::CrashpadInfo<crashpad::process_types::internal::Traits64> > *)0x69085ff000)) [Type: > crashpad::process_types::CrashpadInfo<crashpad::process_types::internal::Traits64>] > > [+0x000] signature : 0x43506164 [Type: unsigned int] > > [+0x004] size : 0x38 [Type: unsigned int] > > [+0x008] version : 0x1 [Type: unsigned int] > > [+0x00c] indirectly_referenced_memory_cap : 0x0 [Type: unsigned int] > > [+0x010] padding_0 : 0x0 [Type: unsigned int] > > [+0x014] crashpad_handler_behavior : 0x0 [Type: unsigned char] > > [+0x015] system_crash_reporter_forwarding : 0x0 [Type: unsigned char] > > [+0x016] gather_indirectly_referenced_memory : 0x0 [Type: unsigned > char] > > [+0x017] padding_1 : 0x0 [Type: unsigned char] > > [+0x018] extra_address_ranges : 0x0 [Type: unsigned __int64] > > [+0x020] simple_annotations : 0x0 [Type: unsigned __int64] > > [+0x028] user_data_minidump_stream_head : 0x0 [Type: unsigned __int64] > > [+0x030] annotations_list : 0x1a3f7238750 [Type: unsigned __int64] > > > I've found Isolate::GetCodeRange but it seems to be used only for setting > up the exception record (v8_crashpad_support::SetUp, > then crash_reporter::internal::RegisterNonABICompliantCodeRangeImpl). > > Is there an established mechanism to report "interesting" memory ranges > from V8 to Crashpad? We'd like to collect the parts of the system heap that > contain Isolate and Heap objects, and the parts of the managed heaps that > are pertinent to the callstack of the crash. > > Thank you! > > P.S. BTW, what is the delineation of topics between v8-dev and v8-users? > > -- > -- > 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. > -- -- 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.
