In "Application Specific Crash Report Information"
(http://mjtsai.com/blog/2013/02/27/application-specific-crash-report-information/)
Michael Tsai notes:
* * * his comments * * *
Wil Shipley shows how an application can add information to a crash
log by assigning to a special string variable. I see the same
technique used in Apple’s source for configd:
/* CrashReporter info */
const char *__crashreporter_info__ = NULL;
asm(".desc ___crashreporter_info__, 0x10");
I also like to use -[NSThread setName:].
* * * end of his comments * * *
I tried this on iOS and did not see any change to a crash report, at
least when the crash report is viewed in Xcode Organizer > Device
Logs.
I basically made a single view iOS project and had this as my ViewController.m:
#import "ViewController.h"
@interface ViewController ()
@end
@implementation ViewController
- (void)viewDidLoad
{
[super viewDidLoad];
// Do any additional setup after loading the view, typically from a nib.
[self addCrashreporterInfo];
[self crash];
}
static const char *__crashreporter_info__ = NULL;
asm(".desc ___crashreporter_info__, 0x10");
- (void)addCrashreporterInfo
{
__crashreporter_info__ = "TestApp 1.0.0";
}
- (void)crash
{
char *addr = 0;
*addr = 1;
}
- (void)didReceiveMemoryWarning
{
[super didReceiveMemoryWarning];
// Dispose of any resources that can be recreated.
}
@end
Anyone have any success using this on technique to annotate crash
reports on iOS?
Chris
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
