Advertise here




Advertise here

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google Sign In with OpenID
Please do not post the same thing multiple times. The board software automatically flags certain posts as needing moderator attention. This happens the most often for new users. I'm pretty sure this is made clear at the time you attempt to post. Posting the same thing over and over again just makes that many more posts the moderators have to weed through later. This makes us sad. Don't make us sad. If your post/thread doesn't appear, just wait a while. Don't post it again. If it hasn't shown up by the next day, then you can try again. I normally go through posts in the mornings, and try to check a few times throughout the day, but I'm not here 24/7. There will typically be a significant delay before posts are approved. Just be patient.

EXC_BAD_ACCESS

ashwinr87ashwinr87 Posts: 115Registered Users
I upgraded to Xcode 4 last week and I am trying to run a program which I developed in Xcode 3...

In my app, I have a navigation toolbar with a table. when i click any cell of the table, it takes me to my next view and in the navigation bar a button comes up which should take me to my previous page. When i press that button to go to the previous page, the following error pops up..

int retVal = UIApplicationMain(argc, argv, nil, nil); where the error is Thread 1: Program received signal : "EXC_BAD_ACCESS".

it works perfectly when i run it on xcode 3 but shows this error on xcode 4..

would someone be able to help me out?

Thanks...
Post edited by ashwinr87 on

Replies

  • ashwinr87ashwinr87 Posts: 115Registered Users
    I figured out where I was going wrong.. before I release a view or anything else, I assigned it to null.. this solved my problem... so for the views, before releasing it, i assigned it to null and for other variables i assigned it to null in - (void) viewDidUnload method...
  • baja_yubaja_yu Posts: 6,166Super Moderators, Registered Users
    That's not a fix. You're just masking poor memory management. If you set it to null first, sending it a release message afterwards is pointless as you are sending release to null. You're probably over-releasing some object. You can use NSZombies to detect such a scenario. Also, the Build & Analyze can discover some issues as well. In any case, I'd take time to read the Memory Management Programming Guide from the documentation.
Sign In or Register to comment.