A NSMutableArray is destroying my life!

Posted by camilo on Stack Overflow See other posts from Stack Overflow or by camilo
Published on 2010-03-24T14:36:04Z Indexed on 2010/03/24 15:23 UTC
Read the original article Hit count: 262

Filed under:
|
|

EDITED to show the relevant part of the code

Hi. There's a strange problem with an NSMutableArray which I'm just not understanding...

Explaining:

I have a NSMutableArray, defined as a property (nonatomic, retain), synthesized, and initialized with 29 elements.

realSectionNames = [[NSMutableArray alloc] initWithCapacity:29];

After the initialization, I can insert elements as I wish and everything seems to be working fine.

While I'm running the application, however, if I insert a new element in the array, I can print the array in the function where I inserted the element, and everything seems ok.

However, when I select a row in the table, and I need to read that array, my application crashes. In fact, it cannot even print the array anymore.

Is there any "magical and logical trick" everybody should know when using a NSMutableArray that a beginner like myself can be missing?

Thanks a lot.

I declare my array as

realSectionNames = [[NSMutableArray alloc] initWithCapacity:29];

I insert objects in my array with

[realSectionNames addObject:[category categoryFirstLetter]];

although I know i can also insert it with

[realSectionNames insertObject:[category categoryFirstLetter] atIndex:i];

where the "i" is the first non-occupied position.

After the insertion, I reload the data of my tableView. Printing the array before or after reloading the data shows it has the desired information.

After that, selecting a row at the table makes the application crash. This realSectionNames is used in several UITableViewDelegate functions, but for the case it doesn't matter. What truly matters is that printing the array in the beginning of the didSelectRowAtIndexPath function crashes everything (and of course, doesn't print anything). I'm pretty sure it's in that line, for printing anything he line before works (example):

NSLog(@"Anything");
NSLog(@"%@", realSectionNames);

gives the output:

2010-03-24 15:16:04.146 myApplicationExperience[3527:207] Anything

[Session started at 2010-03-24 15:16:04 +0000.] GNU gdb 6.3.50-20050815 (Apple version gdb-967) (Tue Jul 14 02:11:58 UTC 2009) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-apple-darwin".sharedlibrary apply-load-rules all Attaching to process 3527.

Still not understanding what kind of stupidity I've done this time... maybe it's not too late to follow the career of brain surgeon?

© Stack Overflow or respective owner

Related posts about nsmutabledictionary

Related posts about xcode