On 23/12/2008, at 10:24 AM, Bill Bumgarner wrote:
Not necessarily. Any number of things can cause crashes like this:
- trashing memory
- thread mis-synchronization
- something goes awry in the malloc zone
That it never happens under Instruments indicates that it might be a
threading issue. Instruments employs some fairly intrusive
interrogation methods and, thus, causes scheduling to be quite a bit
different in a running application being interrogated by Instruments.
Interesting. I'm creating one additional thread explicitly and I will
definitely have a look at that.
I've tried using the MallocStackLoggingNoCompact environment
variable with malloc_history but my results have been inconclusive
at best.
What is the best way to go about looking for this type of bug with
Garbage Collection enabled?
Do you have backtraces from the point of the crash?
I haven't got any that I can post right now, but they are always
different and very rarely contain my code. I will try and make it
crash now and report back!
--
Rob Keniger
_______________________________________________
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
