On 02 Nov 2011, at 8:22 am, Matt Neuburg wrote:
On Nov 2, 2011, at 3:39 AM, Kyle Sluder wrote:
I have to ask why you're printing $eax
You tell me. I'm doing it because Ben Kennedy and a bunch of Web
sites (after a Google search) told me to. m.
And I'll tell you why I did: after being baffled for awhile why my app
was crashing with no console messages (and Xcode showing me main.c), I
decided to manually set breakpoints on objc_exception_throw and -
[NSException raise], hoping that would give me a reasonable chance of
actually seeing, you know, the exception that crashed my app. Of
course "po self" doesn't work there, so I crudely began po'ing every
CPU register (not knowing much at all about ABI conventions) until I
happened on a message that resembled the description string I was
expecting. That happened to be eax in the simulator, and r0 on the
device.
Indeed, I am running Snow Leopard on my Mac Pro. (I don't have much
taste for Lion, so I've thus far relegated it to my MacBook Pro as a
test platform.)
b
--
Ben Kennedy, chief magician
Zygoat Creative Technical Services
http://www.zygoat.ca
_______________________________________________
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
