So far I only looked into the details of how crashpad host and client interact to collect data for a crash, but if we invest into the scenario, it makes total sense to fix 8740 as well.
My understanding is that crashpad has two levels of dumps, small and full. To make the dumps useful I think we should collect the following for v8 (s[mall] is collected for both small and full) 1. (s) pages of the system heap that contain the current Isolate object and a few others, most importantly Heap (need to identify what other objects might be useful for post-mortem debugging) 2. (s) pages of the managed heap that contain jit'ed code and JS objects referenced from the stack at the moment of the crash (how deep would it make sense to recurse? I'd expect we'd want the maps, SFIs, etc. but what else?) 3. (f) all of the managed heap? What if the crash is in GC or some other pure native callstack -- what parts of managed heap could be relevant to collect? Are there any records of the prior discussions wrt integration with crashpad I could look at (bugs, design docs, proposals, etc.)? -- -- 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.
