Download ILCrashReporter for Mac - Crash reporting for developers. MacUpdate.com

ILCrashReporter 1.2.3

Your rating: Now say why...

(2) 3.5

Crash reporting for developers. Free

Add to my Watch List
Email me when discounted

Download Now
176 KB
Visit Developer's Site
Infinite Loop

The ILCrashReporter framework enables developers to easily integrate crash reporting facilities into existing or new applications.

The ILCrashReporter works much like the Crash Reporter built into the operating system. However, for some reason Apple does not provide a way for developers to get access to the reports for their own applications. This problem should be solved by using the ILCrashReporter which will mail the crash reports directly to the developer.

What's New

Version 1.2.3:

Crash reports now contain the machine architecture to help matching stack crawls from universal binaries.
Attached console logs are now limited to 512 KB to prevent overloading email accounts.

Requirements
PPC / Intel, Mac OS X 10.2 or later.

Be the first to recommend a similar software title.

ILCrashReporter User Discussion (Write a Review)

ver. 1.x:

(2)

Your rating: Now say why...

Overall:

(2)

sort: smiles | time

-2

Kballard commented on 24 Nov 2005

I would encourage people to take a look at Smart Crash Reports . This seems to be similar to SCR except on a per-app basis and not as powerful.

[Version 1.2.3]

Anonymous reviewed on 22 Dec 2004

I completely agree with the developer, this is quite cool. Also I agree I could have probably have writen it myself with some effort, but I never have a problem when someone alse does it all! Indeed, often the comments on what the user was doing before a crash is the useful ionformation that might be hard to get from the report. So I am going to offset the rating a bit.

But I have some requests:
- Why not make the source available, it makes it easier to embed it into an application.
- Can there be an (optional) Cancel button, and for the Send button: I am not Apple...

[Version 1.1]

Anonymous reviewed on 12 Oct 2004

This is a cool idea, even a very good idea, but wherein lies the difficulty for developers to do this? To wit:

1. Crash reports are always named by application name. Extension 'log', right?

2. They are always located in ~/Library/Logs/CrashReporter.

3. All you have to do is guard your code in an exception handler and call the messaging framework API if an exception is thrown.

[NSMailDelivery
deliverMessage:
[NSString stringWithContentsOfFile:
[[[@"~/Library/Logs/CrashReporter]
stringByAppendingPathComponent:@"MyApp.log"]
stringByExpandingTildeInPath]]
subject:@"Crash Report - My App"
to:@"acme@acme.com"];

To me, that is never going to compile to 62 KB. Maybe a 15th of that tops.

[Version 1.0.1]

1 Reply

Anonymous commented on 16 Oct 2004

1 and 2 I fully agree - that's actually how ILCrashReporter gets the reports.

But I do not agree on 3 since you would not have any crashlogs generated automatically if you made your own exception handling. Furthermore it would only catch exceptions and not regular crashes.
Your code example would also require that the computer has a fully configure email account. Besides what about asking the user for comments about what lead to the crash or even the permission to send information about his computer?

The 62k contains framework with userinterface, documentation, sample code, etc. so I doubt it could be made much smaller.

There are currently no troubleshooting comments. If you are experiencing a problem with this app, please post a comment.

There are currently no ratings. Write a comment or review now.