Follow-up re the execution issue.
The source of the crash seems to be the creation of an object using another class, to wit:
[[[[ProcessHandler alloc] init] autorelease]
createProcObjectFor:[processName stringValue] autorelease];
where ProcessHandler is a class whose primary job is to create named objects, a la:
if( [setName isEqualToString:@"nameN"] )
return [[ProcessorN alloc] init];
and processName is a Text Field IBOutlet.
The same behavior (crash) happens if I release the object at the end of the IBAction code rather autoreleasing at creation.
Debugging shows that the created object acts as expected. Apparently the problem relates to its release (or lack there of).
As noted before, this scheme of object creation and release ran without a problem under OS X 10.5.
On Sep 16, 2009, at 3:42 PM, dct wrote:
Since installing OS X 10.6 and Xcode 3.2 (64-bit) I've encountered (1) an irritating debugger display problem and (2) a crash situation that wasn't there prior to this installation.
Debugger. The debugger window opens but the editor pane never loads--neither initially nor as I step through breakpoint to breakpoint. The thread and variable panes do load and perform as expected. I assume that there is a setting to be made with the new Snow Leopard configuration but I haven't found it.
New crash. Code that has been compiling and running for several years now fails after a specific UI operation. The IBAction code for the operation runs to completion without a hitch and then the crash occurs with (sometimes) a screen identifying a "CFBasicHashDeallocateError". This code does allocate/init/autorelease one object, gets the string value of a ComboBox, and sets the state of a Push Button but little else. What am I up against and why does Snow Leopard object when Leopard didn't?