Grabbing this. It's a change that started a couple of weeks ago when we switched to the new rust-minidump stackwalker which now always emits a `mac_crash_info` section. The real problem here is that I didn't really know how we were going to use the `mac_crash_info` data, didn't know what questions we were trying to answer using search, or how to index it when I was working on bug #1748248. Because of that, it's never been very usable and there are a few bugs stemming from that. (bug #1714190, bug #1713355) I don't think we should change rust-minidump stackwalker. Instead, we should go back and figure out what questions are we trying to answer, what does the `mac_crash_info` structure look like, and how we want to index it so that we can answer the questions we want to answer.
Bug 1748248 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Grabbing this. It's a change that started a couple of weeks ago when we switched to the new rust-minidump stackwalker which now always emits a `mac_crash_info` section. The real problem here is that I didn't really know how we were going to use the `mac_crash_info` data, didn't know what questions we were trying to answer using search, or how to index it when I was working on bug #1709658. Because of that, it's never been very usable and there are a few bugs stemming from that. (bug #1714190, bug #1713355) I don't think we should change rust-minidump stackwalker. Instead, we should go back and figure out what questions are we trying to answer, what does the `mac_crash_info` structure look like, and how we want to index it so that we can answer the questions we want to answer.