On Sun, Jun 29, 2008 at 9:56 AM, David Troy <[EMAIL PROTECTED]> wrote: > I have a situation where I am loading arbitray data from network-supplied > URLs. Sometimes the URLs contain Kanji unicode characters. When they do, > my HTTP loading mechanism (which is built around NSURL* frameworks) dies > with an exception deep inside of CFURLGetString.
This sounds like it might be a bug, although I can't imagine no one's tried this before. > Short of writing code to protect CFURLGetString from ever seeing one of > these URLs, I thought the simplest thing to do would be to try to cover this > section of code with a @try/@catch construct, but it seems to be having no > effect. The program still crashes. I gather it is because what I'm getting > is a null pointer type of issue, rather than something that generates a > manageable NSException object. Yes. If the error message contains the word "unhandled exception", then you're getting an NSException. If you see the word "SIGBUS" or "SIGSEGV" then there's a bad pointer somewhere. However, the issue you're describing doesn't sound like it would be generating an NSException. I have no experience with URLs containing characters beyond 0x7F, so I can't help you much beyond that. Owen _______________________________________________ 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 [EMAIL PROTECTED]
