FROM : Ben Trumbull
DATE : Thu Mar 13 21:25:16 2008
All,
For ADC members, debug libraries for 10.5, and now 10.5.1 & 10.5.2,
are available in the Developer Tools section of Downloads as "Debug
and Profile Libraries for Mac OS X 10.5".
There's a tech note about how to use these frameworks with
DYLD_IMAGE_SUFFIX. 'man dyld' also works.
Since there are many different debug libraries, one might consider
renaming the suffix for just the libraries with which you currently
need to work. (i.e. CoreData_debug -> CoreData_threading)
For Core Data developers, the most interesting aspect of this is the
addition of assertions to enforce Core Data's multi-threading policy.
You can enable these assertions by setting the user default
-com.apple.CoreData.ThreadingDebug 3
(in cmd line style)
This works best run in gdb with some additional breakpoints:
future-break handleFailureInMethod:object:file:lineNumber:description:
future-break handleFailureInFunction:file:lineNumber:description:
future-break malloc_printf
As a tangent, while not necessarily errors, I find it useful to
sometimes toggle these:
future-break raise:format:arguments:
future-break objc_exception_throw
future-break +[NSError errorWithDomain:code:userInfo:]
--
-Ben
DATE : Thu Mar 13 21:25:16 2008
All,
For ADC members, debug libraries for 10.5, and now 10.5.1 & 10.5.2,
are available in the Developer Tools section of Downloads as "Debug
and Profile Libraries for Mac OS X 10.5".
There's a tech note about how to use these frameworks with
DYLD_IMAGE_SUFFIX. 'man dyld' also works.
Since there are many different debug libraries, one might consider
renaming the suffix for just the libraries with which you currently
need to work. (i.e. CoreData_debug -> CoreData_threading)
For Core Data developers, the most interesting aspect of this is the
addition of assertions to enforce Core Data's multi-threading policy.
You can enable these assertions by setting the user default
-com.apple.CoreData.ThreadingDebug 3
(in cmd line style)
This works best run in gdb with some additional breakpoints:
future-break handleFailureInMethod:object:file:lineNumber:description:
future-break handleFailureInFunction:file:lineNumber:description:
future-break malloc_printf
As a tangent, while not necessarily errors, I find it useful to
sometimes toggle these:
future-break raise:format:arguments:
future-break objc_exception_throw
future-break +[NSError errorWithDomain:code:userInfo:]
--
-Ben
| Related mails | Author | Date |
|---|---|---|
| No related mails found. | ||






Cocoa mail archive

