Effect of NSLog() while running under the debugger
Effect of NSLog() while running under the debugger
- Subject: Effect of NSLog() while running under the debugger
- From: Rick Mann <email@hidden>
- Date: Thu, 4 Feb 2010 11:05:35 -0800
I have some code that uses a library from a company for user-land USB access (the library uses libusb to do this). It generally works, but I've run into an issue where it eventually gives me a nasty-looking error, and then crashes with EXEC_BAD_ACCESS.
Interestingly, though, this only happens when I run under the debugger in Xcode, and does not happen when I launch my app from the Finder. My first thought is that the duration of NSLog() calls is different when running under the debugger, enough to cause whatever the condition is down in the library to manifest itself.
FWIW, here's the scary error message I see:
2/4/10 09:48:59 MyApp[63404] In '__CFRunLoopLock', file /SourceCache/CF/CF-550.13/RunLoop.subproj/CFRunLoop.c, line 438, during lock, spin lock 0x7fffffe00316 has value 0x483b9aca, which is neither locked nor unlocked. The memory has been smashed.
TIA,
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden