One of my customers on OS X 10.5.8 is reporting a crash when my app
uses the NSLog command. It seems like his computer is having
difficulty timestamping the log, as can be seen from the relevant part
of the crash log below:
Thread 1 Crashed:
0 libSystem.B.dylib 0xffff0680 __bzero + 128
(cpu_capabilities.h:244)
1 com.apple.CoreFoundation 0x94e7d160 CFTimeZoneCreate +
544
2 com.apple.CoreFoundation 0x94e7d8d9
CFTimeZoneCreateWithName + 409
3 com.apple.CoreFoundation 0x94e7e13f
CFTimeZoneCopySystem + 687
4 com.apple.CoreFoundation 0x94e7e21f
CFTimeZoneCopyDefault + 95
5 com.apple.CoreFoundation 0x94def4e5
CFCalendarCreateWithIdentifier + 197
6 com.apple.CoreFoundation 0x94e95627 __CFLogCString + 743
7 com.apple.CoreFoundation 0x94e9592b _CFLogvEx + 299
8 com.apple.Foundation 0x9385ec5e NSLogv + 174
9 com.apple.Foundation 0x938be1db NSLog + 27
I cannot replicate this crash but I have seen this happen with other
applications too. Is this my bug or Apple's? Is there anything I can
do to prevent it?
Thanks,
Mark.
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
