I'm not sure when this happened exactly, but "recently" as I know I followed a link from a Camino 2.0.7 crash report to bonsai-cvs on July 26, so at least Camino 2/cvs.mozilla.org was still working at that point. It's more difficult for me to determine when I last followed a link to hgweb from a crash report, but I'm pretty sure I did so within the last week or two. In the URL in the URL field, there is a wide selection of reports from various products and branches, crashing on various dates, and none of them that I have looked at have any of the source lines linkified. (In addition, all the crashes in https://crash-stats.mozilla.com/report/list?product=Camino&version=Camino%3A2.1a2pre&platform=mac&query_search=signature&query_type=exact&reason_type=contains&date=08%2F01%2F2011%2023%3A56%3A42&range_value=4&range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=objc_msgSend%20|%20SampleMouseAndKeyboard have no source lines at all; it's possible this is a different problem, though.)
We actually just rolled out the Socorro 2.1 release today, and due to bug 665986 source links should be maintained automatically now. I see working links on https://crash-stats.mozilla.com/report/index/fdb36a71-de73-4a9e-ab9f-8a9412110731 Can you give an example where it's broken? The old system needed to be bumped everytime there was a release, so it would quickly get out of date. (In reply to comment #0) > (In addition, all the crashes in > https://crash-stats.mozilla.com/report/ > list?product=Camino&version=Camino%3A2. > 1a2pre&platform=mac&query_search=signature&query_type=exact&reason_type=conta > ins&date=08%2F01%2F2011%2023%3A56%3A42&range_value=4&range_unit=weeks&hang_ty > pe=any&process_type=any&do_query=1&admin=1&signature=objc_msgSend%20|%20Sampl > eMouseAndKeyboard have no source lines at all; it's possible this is a > different problem, though.) I don't know what the problem here is, these don't look like source code lines to me though. This looks like missing symbols or something.
(In reply to comment #1) > Can you give an example where it's broken? The old system needed to be > bumped everytime there was a release, so it would quickly get out of date. I just looked again at every report I looked at this afternoon, and they're all linkified now. Perhaps I was getting a stale cache or the like from the webapp this afternoon when I was at the office? At any rate, unless I have the problem again tomorrow af the office, we can write it off to transient internet gremlins ;-) > > (In addition, all the crashes in > > I don't know what the problem here is, these don't look like source code > lines to me though. This looks like missing symbols or something. The recent one (build 20110712090012) was not a nightly build, so it wouldn't have symbols; the others are a nightly build from May(!), so I guess it's possible its symbols have been purged already. (With missing symbols, I would have expected the frames to be raw addresses rather than resolved methods, which is why I thought it might have been related to the line-linkification issue.) At any rate, I don't care about a non-nightly build and May nightlies, so unless I see the problem again in recent builds, this item is WFM, too. Sorry for the "false" alarms, and thanks for checking so quickly!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.