NSMutableArray remove Object is cloning another object in the Array

Question

I have an strange error after removing an object in a NSMutableArray.

Before deleting an object

If i remove an object with

[Array removeObjectAtIndex:2];

the array changed to this:

enter image description here

why are there now 2 ContactViewControllers??

+1 Excellent question. Did you notice that the original `SolutionViewController` at index 6 has gone missing too? — trojanfoe, Feb 12 '13 at 13:54
This has nothing directly to do with our question, but do yourself a favor and don't use uppercase object/variable names. In Objective-C, only classes, interfaces and the like should have uppercase names. — mrueg, Feb 12 '13 at 14:03
how are you able to expand an array in the debug mode (like your screen shots)? i can't seem to do it.. — David Ben Ari, Feb 12 '13 at 14:04
Obviously via breakpoint. i still don't see. i'll stop spamming this post and ask a Question.. — David Ben Ari, Feb 12 '13 at 14:09
@DavidBenAri [Xcode 4.6](http://developer.apple.com/library/ios/#releasenotes/DeveloperTools/RN-Xcode/index.html#//apple_ref/doc/uid/TP40001051-SW216) — Alladinian, Feb 12 '13 at 14:18

score 7 · Accepted Answer · answered Feb 12 '13 at 14:16

7

lldb lies sometimes. It gets confused and will display the incorrect information. Try doing

po Array

you should see the correct array contents then.

answered Feb 12 '13 at 14:16

ahwulf

2

This is scary... I thought Apple would've fixed [this bug](http://stackoverflow.com/questions/10963268/float-variables-assigned-value-from-line-above/10963683#10963683) by now – Alladinian Feb 12 '13 at 14:31
Yes it's quite stupid. lldb will often fail to showing anything up the stack, and sometimes confuses one variable with another. – ahwulf Feb 12 '13 at 21:32

1 Answers1