Re: XCode 2.4 crashes debugging Dwarf (was: on Intel iMac)
Re: XCode 2.4 crashes debugging Dwarf (was: on Intel iMac)
- Subject: Re: XCode 2.4 crashes debugging Dwarf (was: on Intel iMac)
- From: Shawn Erickson <email@hidden>
- Date: Sun, 20 Aug 2006 08:42:36 -0700
On Aug 19, 2006, at 7:46 PM, Jeremy Sagan wrote:
These persistent XCode crashes related to debugging apparently have
very little, or nothing, to do with being on Intel. I can pretty
consistently get it to occur on a PPC machine as well. This is a
fresh build after a 'clean'. Xcode crashes after hitting a
breakpoint when I try to step through the code.
Its strange to me that no one at Apple seems to be interested in a
serious bug like this.
The console always says something like:
===== Saturday, August 19, 2006 9:21:36 PM US/Eastern =====
2006-08-19 22:08:50.432 Xcode[16277] Error in CGSAddTrackingRect
(-301)
2006-08-19 22:08:50.434 Xcode[16277] Error in CGSAddTrackingRect
(-301)
2006-08-19 22:08:50.436 Xcode[16277] Error in CGSAddTrackingRect
(-301)
Xcode(16277,0xa000ed98) malloc: *** vm_allocate(size=20480) failed
(error code=-301)
Xcode(16277,0xa000ed98) malloc: *** error: can't allocate region
Xcode(16277,0xa000ed98) malloc: *** set a breakpoint in szone_error
to debug
Aug 19 22:09:05 Powerbook133 crashdump[27541]: Xcode crashed
Aug 19 22:09:09 Powerbook133 crashdump[27541]: crash report written
to: /Users/Jerm/Library/Logs/CrashReporter/Xcode.crash.log
==================================
Looks like a memory leak in Xcode (or possibly you are debugging a
really large binary?) is exhausting Xcodes virtual memory space.
Anyway report the crash to Apple via bugreporter... <http://
bugreporter.apple.com/>
-Shawn
_______________________________________________
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