[Adium-devl] (no subject)

[Slava Karpenko]

Hi,

Apologies for the delayed reply. Been busy getting all of our stuff  
i386-ready. =)

> 1) We currently launch our crash reporter not only when a crash  
> occurs but also when an unhandled exception is thrown, since  
> unhandled exceptions nearly universally lead to undesirable  
> behavior.  The NSExceptionHandling framework is used so we can  
> report a stack trace for the exception [1]; exception crash reports  
> are formatted just like normal OS X crash reports, including build  
> number, OS X version, stack trace, and so on, with the addition of  
> the exception's name and reason.  All this information is written  
> by Adium to a text file; Adium then launches the Adium Crash  
> Reporter and quits itself.
>
> This amounts to an API request for SCR: could there be a function  
> which allowed immediate launching of the reporter, pointing it to a  
> specific crash log (or, in this case, exception log), so we could  
> maintain this existing and extremely useful functionality while  
> moving to SCR?
	That's pretty much possible, except for one interesting point: the  
same thing would get sent to Apple, and I don't think their scripts  
expect anything that falls out of the standard crash report format.  
There's a chancel we'll be breaking Apple's side (or at least will  
annoy them with the extra stuff). One suggestion would be to use  
UnsanitySCR_RegisterMatchSpecifier call to provide any extra  
information you want in the user comments field (ie, the exc handler  
catches the exception, calls the abovementioned function and then  
terminates the app, SCR will do the rest).

	I can still add a call to directly invoke CrashReporter.app from  
within SCR API, I think. What are your thouights on this?

> 2) Statistics.  One of the biggest weaknesses of our current system  
> is that there is no useful way to get crash statistics. A  
> ridiculously powerful view, for example, would be a display of each  
> unique crash (by crashlog), sorted by number of times that crash is  
> reported.  More simple stats like a display of which modules have  
> the most crashes reported, etc., would also be very helpful.  It's  
> my understanding that this is part of how Apple makes the crash  
> reports they receive more manageable.  Any thoughts?

	Well, we base our web interface off the code contributed by Timothy  
Hatcher -- it's all PHP, so if someone volunteers to tweak it to do  
what you want (we store the crash logs we get in a MySQL database), I  
am more than willing to share the code for that so all developers  
using SCR could benefit from that.

	Either way, since this is a free community project, I am always open  
for suggestions and contributions. ;)

Sincerely yours,
Slava Karpenko
Unsanity

:: slava at unsanity.com
:: www.unsanity.com / www.haxies.com / www.unsanity.org
-- 
Unsanity - Unsane Tools For Insanely Great People - Haxies for Mac OS X

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2365 bytes
Desc: not available
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20060128/bae72775/attachment.p7s>