Re: gdb warning: Couldn't find class validation function
Re: gdb warning: Couldn't find class validation function
- Subject: Re: gdb warning: Couldn't find class validation function
- From: Jeff Johnson <email@hidden>
- Date: Wed, 23 Jun 2010 20:58:43 -0500
Ok, I've discovered that the gdb hanging was actually caused by a thread deadlock in custom -debugDescription methods. After deleting debugDescription, the hangs no longer occur. However, the gdb warning is still there, so that's still puzzling, though it's apparently not causing other problems.
-Jeff
On Jun 23, 2010, at 7:48 PM, Jeff Johnson wrote:
> I'm having trouble debugging some Objective-C code in an embedded framework in my Cocoa application. The print-object command is sometimes causing gdb to hang. When gdb is stopped in one of my class's instance methods, the following works fine:
>
> (gdb) p [self output]
>
> but this outputs a warning and then hangs (until I do a SIGINT):
>
> (gdb) po [self output]
> warning: Couldn't find class validation function, calling methods on uninitialized objects may deadlock your program.
>
> The method -output is defined in my class's superclass. The warning doesn't make a lot of sense to me, because none of the objects are uninitialized. If I put an NSLog() of [self output] in the code there, it works as expected.
>
> Not all calls cause gdb to hang, though. Some print-object commands on my object succeed, others fail.
>
> Does anyone know why this would occur? It's making it difficult for me to debug my framework. The problem occurs with Xcode 3.2.3 (and with [redacted]) on 10.6.4.
>
> -Jeff
_______________________________________________
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