(Following up comment #0) > 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. This going to take me longer than I expected, because it's a lot more complicated than I expected. I may end up recommending that we not make public the `__crash_info` data from certain modules. But doing that prematurely may end up making it impossible to do the research required to find out whether or not information from those modules' `__crash_info` modules is too sensitive. I'll have at least a preliminary report available either later today or sometime tomorrow.
Bug 1709658 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(Following up comment #0) > 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. This going to take me longer than I expected, because it's a lot more complicated than I expected. I may end up recommending that we not make public the `__crash_info` data from certain modules. But doing that prematurely may end up making it impossible to do the research required to find out whether or not information from those modules' `__crash_info` sections is too sensitive. I'll have at least a preliminary report available either later today or sometime tomorrow.
(Following up comment #0) > 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. This going to take me longer than I expected, because it's a lot more complicated than I expected. I may end up recommending that we not make public the `__crash_info` data from certain modules. But doing that prematurely may end up making it impossible to do the research required to find out whether or not information from those modules' `__crash_info` sections is too sensitive. I'll have at least a preliminary report available either later today or sometime tomorrow. Edit: It's going to be sometime tomorrow.