Rick, you can use po and than most of what you are used in Obj-C like you would use in NSLog.
Or just use NSLog and any of the properties a NSError has. Cheers, Volker Am 14.10.2009 um 19:30 schrieb Rick Mann: > > On Oct 14, 2009, at 09:57:58, Kyle Sluder wrote: > >> On Wed, Oct 14, 2009 at 9:44 AM, Rick Mann <rm...@latencyzero.com> wrote: >>> Breaking on all -presentError:, it finally stops here: >> >> Okay, this is the point at which you examine the NSError and see if it >> has any more information for you. :) > > Is there a way I can get at that programmatically, rather than via gdb? I'm > very clumsy in gdb. > _______________________________________________ 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
