Patches have just been landed at bug 1577886 to add support for `__crash_info` data to Breakpad. Another is about to be landed at https://github.com/mozilla-services/minidump-stackwalk/pull/29. I'm opening this follow up bug to deal with two tasks: 1) Make a summary of `__crash_info` data (if present) available on the "details" page of crash reports at https://crash-stats.mozilla.org/. 2) Make this data searchable. Once the second patch has landed, `__crash_info` data will be available on the "raw data" page of crash reports. But its format won't be particularly user-friendly, and of course it won't (yet) be searchable. Gabriele [has pointed out](https://github.com/mozilla-services/minidump-stackwalk/pull/29#issuecomment-832802599) that before we make either of these changes, we need to make sure this data doesn't contain user-sensitive information. Apple's `__crash_info` data is completely undocumented, beyond a few references to it in the source code available at https://opensource.apple.com/. But it's only system modules that contain a `__crash_info` section. So the information in them can only be very low-level. For example I'd be surprised if it could contain URLs. I'd expect the concept of a URL to only be understandable by higher-level, Mozilla-specific code. I have a lot of experience reverse-engineering macOS, so this is something I can try to check. I'll spend a few hours doing that and report back. By the way, I only have the vaguest notion of "user-sensitive information". Is there a good definition of it somewhere, that I can rely on?
Bug 1709658 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Patches have just been landed at bug 1577886 to add support for `__crash_info` data to Breakpad. Another is about to be landed at https://github.com/mozilla-services/minidump-stackwalk/pull/29. I'm opening this follow up bug to deal with two tasks: 1) Make a summary of `__crash_info` data (if present) available on the "details" page of crash reports at https://crash-stats.mozilla.org/. 2) Make this data searchable. Once the GitHub pull request has landed, `__crash_info` data will be available on the "raw data" page of crash reports. But its format won't be particularly user-friendly, and of course it won't (yet) be searchable. Gabriele [has pointed out](https://github.com/mozilla-services/minidump-stackwalk/pull/29#issuecomment-832802599) that before we make either of these changes, we need to make sure this data doesn't contain user-sensitive information. Apple's `__crash_info` data is completely undocumented, beyond a few references to it in the source code available at https://opensource.apple.com/. But it's only system modules that contain a `__crash_info` section. So the information in them can only be very low-level. For example I'd be surprised if it could contain URLs. I'd expect the concept of a URL to only be understandable by higher-level, Mozilla-specific code. I have a lot of experience reverse-engineering macOS, so this is something I can try to check. I'll spend a few hours doing that and report back. By the way, I only have the vaguest notion of "user-sensitive information". Is there a good definition of it somewhere, that I can rely on?