EXC_BAD_ACCESS error when changing views with PresentModalViewController?

I suggest that you declare variable1 variable2 and variable3 as properties, not instance variables. Then, use self. Variable1 self.

Variable2 and self. Variable3 to access them.

I suggest that you declare variable1, variable2, and variable3 as properties, not instance variables. Then, use self. Variable1, self.

Variable2, and self. Variable3 to access them. The dot syntax (self.

Variable1, etc. ) uses the memory management policy you declared on each property; the arrow syntax (self->variable1, etc. ) will access the variables directly. The crash is because you created two arrays in away that doesn't leave you owning them, and then did not assign the arrays to a property that would retain them. You may also want to upgrade your project to use ARC.

Then there is no memory-management difference; assigning to the instance variables rather than the properties will not cause the object to be prematurely released, because ARC considers instance variables to be ownerships by default. You may still want to switch to using properties after you switch to ARC, but not to prevent a crash. In response to your edit: I change the way I declare my variables to @property/@synth to clean up my code, but it didn't fix the problem.

Then something else was wrong. You never did say much about the problem itself. You said you got an EXC_BAD_ACCESS, but not what statement triggered the crash or on what grounds you blamed it on the code you showed.

I changed the code from this: self. Variable1 = NSNumber alloc initWithInt:0; That's the correct code, though. That's what you should be using.

To this: self. Variable1 = NSNumber alloc; self. Variable1 initWithInt:0; Noooo!

That code is wrong, wrong, wrong, on multiple levels. Init methods (including initWithWhatever: methods) are not guaranteed to return the same object you sent the message to. NSNumber's initWithInt: very probably doesn't.

That object creates an uninitialized NSNumber object and assigns that to the property. Then it sends initWithInt: to that object, which will return an initialized object, which can be and very probably will be a different object. Now you are holding an uninitialized object (which you will try to use later) and have dropped the initialized object on the floor.

Never, ever, ever send alloc and init(With…) in separate expressions. Always send them in the same expression. No exceptions.

Otherwise, you risk holding the uninitialized object rather than the initialized object.In your case (with NSNumbers), that is almost certainly what will happen. What you should be doing is declaring and synthesizing a strong property that owns the NSNumber object, and creating the NSNumber object in a single statement: either NSNumber alloc initWithInt: or NSNumber numberWithInt:. If you're not using ARC, you'll want the latter, since the property will retain the object.

If you are using ARC, they're effectively equivalent. And if you get a crash with that code, then something else is wrong, so please tell us—either in this question or in a new question—about the crash so we can help you find the true cause of it.

Variable2 and variable3 are being autoreleased before you actually access them (presumably) later after presenting the modal view. At the very least change the lines to: self->variable2 = NSMutableArray arrayWithCapacity:1 retain; self->variable3 = NSMutableArray arrayWithCapacity:1 retain; or self->variable2 = NSMutableArray alloc initWithCapacity:1; self->variable3 = NSMutableArray alloc initWithCapacity:1; variable1 should be fine. Best would be to use @property and @synthesize so you can use dot notation: .

H @interface MyClass : SuperClass @property (nonatomic,retain) NSMutableArray *variable2; @property (nonatomic,retain) NSMutableArray *variable3; @end . M @implementation MyClass @synthesize variable2,varible3; - (void)foo { self. Variable2 = NSMutableArray arrayWithCapacity:1; self.

Variable3 = NSMutableArray arrayWithCapacity:1; } @end.

By default, all instance variables in objective-c have protected scope. So unless you have explicitly declared them public in your interface file as: @interface MYClass { @public NSNumber *variable1; NSMutableArray *variable2; NSMutableArray *variable3; } //... @end then they will not be accessible using the struct dereferencing operator. This is likely the cause of those EXC_BAD_ACCESS errors.

The compiler would have thrown errors and prevented the build in the first place. So, this would not be the case. – gschandler Dec 9 at 4:02.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.