Thank you,
I think I am going for the second choice, with the helper (An
directoryobserver that runs in a runloop should do the trick? Right?).
If I go without the helperthread, then you do not have any control
over when the error will be submitted. The user might never ever try
to run the app again...
Filip van der Meeren
[email protected]
http://sourceforge.net/projects/xlinterpreter
On 17 Apr 2009, at 16:21, Scott Ribe wrote:
Is there any way for me to view the errors my users
are sending; or should I implement such a function myself.
Two general approaches:
- SmartCrashReporter, which is easy & convenient for you since it's
prepackaged. Also somewhat controversial since it injects code into
every
app launched. (Hint: disclose its use, and make the install optional
if you
want to avoid criticism.)
- On launch, check for new crash reports and send them to yourself
(~/Library/Logs/CrashReporter/...) Note that 10.4 appends new
reports to a
single file per application, while 10.5 creates one file per crash,
with
different naming conventions.
And a variant of that second one:
- If you're really ambitious, launch a background helper process to
monitor
for crash reports as soon as they happen--probably way overkill for
most
situations.
--
Scott Ribe
[email protected]
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
