On May 30, 2011, at 9:55 AM, Ken Thomases wrote: > I'm guessing that whatever method vended the string didn't do so with the > bycopy qualifier. Therefore, you have a proxy of the string object and any > messages you send it require communication with the server.
It definitely sounds like a proxy got vended by mistake … but that shouldn’t happen with an NSString because those are always sent as bycopy by default. My best guess is that the ‘vendedString’ pointer isn’t actually pointing to an NSString — there may be some bug in the app that actually passes an object of some other class that does get proxied. Ken T: To verify that this is a deadlock, try sampling the app when it locks up (or breaking in gdb and looking at the current stack of that thread.) We’re guessing it’ll be in some DO remote-call code waiting for a response from the socket. Also try putting in an isKindOfClass check before the problematic line to make sure that vendedString is actually an NSString. —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
