Apple

I'd say your most likely point of failure is in using the result of -[NSString cStringUsingEncoding:]. Both the declaration in NSString.h as well as the documentation for that method list a number of caveats including a possible buffer deallocation in some cases. A safer method would be -[NSString getCString:maxLength:encoding:] since you control when the buffer is deallocated.

On Aug 30, 2009, at 2:00 PM, Charlie Dickman wrote:

Greetings,

When debugging in Xcode 3.2 (Snow Leopard) the following code "works" but, sometime later, causes addressing exception in the apps run loop...

NSArray *filesToOpen, *fileTypes = [NSArray arrayWithObject: @"txt"];
NSOpenPanel *oPanel = [NSOpenPanel openPanel];
NSString *fileToOpen;
const char *fileToRead = NULL;
[oPanel setAllowsMultipleSelection: NO];
[oPanel setResolvesAliases: YES];
[oPanel setTitle: @"IOSilver script file"];

if ([oPanel runModalForTypes: fileTypes] == NSOKButton) {
filesToOpen = [oPanel filenames];
fileToOpen = [filesToOpen objectAtIndex: 0];
fileToRead = [fileToOpen cStringUsingEncoding: NSASCIIStringEncoding];
[self constructScriptFromFileNamed: fileToOpen];
}

Further, when used without the debugger it causes all sorts of strange results regarding subsequent events such as keypresses.

Any comments or ideas as to what's up would be greatly appeciated.

References:
	>NSOpenpanel in Snow Leopard (From: Charlie Dickman <email@hidden>)