Macs need better crash logs #1601
Comments
Buginator commented Here is a example of the crashlog that we need the mac's to look like. http://developer.wz2100.net/attachment/ticket/2242/warzone2100.gdmp-dCeF0K
All that is missing from mac's current crash reports. Something like:
:) |
dak180 commented Replying to Warzone2100/old-trac-import#1601 (comment:2):
Actually all that (except for the language and the map name) is already in the report. The local vars though are missing. |
Buginator commented Replying to Warzone2100/old-trac-import#1601 (comment:3):
All the stuff after Misc Data: (which is what we add to all the crash dumps), and I don't recall if we know show if the Mac build is a release / debug build, or the Distributor is mentioned. |
dak180 commented Replying to Warzone2100/old-trac-import#1601 (comment:4):
There is no mention of a distributor in the mac reports (but is that something we really need?); as for saying if it is a debug build or not, currently it does not, but I could add a note to the version string for debug builds if you like. |
dak180 commented Just found this; it may prove useful. |
vexed changed type from |
keyword_log_crash
type_task
| by dak180The following are some links that may help with this.
http://briksoftware.com/blog/?p=58
http://blogs.embarcadero.com/eboling/2009/11/10/5628
http://www.brianweb.net/misc/mach_exceptions_demo.c
Issue migrated from trac:1601 at 2022-04-15 21:07:08 -0700
The text was updated successfully, but these errors were encountered: