Josh noted while looking into bug 520058 that having module version info would be useful for diagnosing such crashes. Currently, it looks like we don't have any version info reported for modules on OS X. This has also been really useful info to have on other platforms.
There are a couple of issues filed upstream on this: http://code.google.com/p/google-breakpad/issues/detail?id=303&q=version http://code.google.com/p/google-breakpad/issues/detail?id=321 That first one has a patch, that might be what we want. Breakpad has code to do this, but unfortunately there are two code paths: in process and out-of-process, and it only got implemented in the latter, and we use the former...
dolske, see also bug 503181, of which this is sort-of a dupe. As noted there, even if the in-process codepath had version detection, it still won't help with Flash because of Breakpad issue 321 and Flash's Info.plist. Frustrated at every turn!
collecting both values determined by bug 503181 comment 2 plus a module checksum would be nice. sure it costs something, but :)
It not only costs something, it might be impossible to do safely without out-of-process minidump generation.
i was thinking we could collect some of this data in the standalone reporter app. it's the thing which has the restart button, right? it could be evil and record the modules that are loaded when firefox is restarted. it won't necessarily be accurate, but it will give us some idea, as long as we have enough checksums for the old + new binaries to confirm whether they match. if they don't, then ideally someone else's reporter will have sent in the right general information and we'll collate against theirs server side :)
Bug 412633 will collect plugin version info (which is what I was originally looking for here), but I think we should leave this open for the general case of non-plugin module info.
You need to log in before you can comment on or make changes to this bug.