iphone – 在访问OCMock中的参数时,EXC_BAD_ACCESS

在这种情况下,UIImageView扩展类正在测试.我想检查扩展名是否调用[self setImage：],其参数为非零(稍后将使用其他图像比较).

当使用OCMock和方法时,块完成后,测试将以EXC_BAD_ACCESS崩溃.

id mockView = [OCMockObject mockForClass:[UIImageView class]];
[[[mockView stub] andDo:^(NSInvocation *invocation)
  {
      UIImage *img;
      [invocation getArgument:&img atIndex:2]; <---- line causing the exception
      somebodySetImage |= (img != nil);

  }] setImage:OCMOCK_ANY];

  [mockView do_something_that_calls_setImage];

我现在找到的唯一解决方案是使用andCall而不是andDo,但这使测试复杂化.

我可以避免碰撞吗？

UPDATE
嗯,我会尝试在这里给一个更好的例子：
这是新的测试代码：

- (void)testDownloadingThumbnail
{
    PInfo *_sut = [[PInfo alloc] init];

    __block id target = nil;

    id mock = [OCMockObject mockForClass:[NSOperationQueue class]];

    [[[mock expect] andDo:^(NSInvocation *inv)
    {
        NSInvocationOperation *op;
        [inv getArgument:&op atIndex:2];
        target = [[op invocation] target]; /* replacing this line with STAssert does not help either */
    }] addOperation:OCMOCK_ANY];

    [_sut setDownloadQueue:mock];
    [_sut startDownloadingImagesAsync:YES];

    [mock verify];

    STAssertEqualObjects(target,_sut,@"invalid op target");
}

这是测试代码(PInfo的单一方法)：

- (void)startDownloadingImagesAsync:(bool)isThumbnailImg
{
    NSInvocationOperation *inv;

    inv = [[NSInvocationOperation alloc] initWithTarget:self
                                     selector:@selector(loadThumbnailWorker:)
                                       object:nil];
    [[self downloadQueue] addOperation:inv];
}

从EXC_BAD_ACCESS的startDownloadingImagesAsync退出时代码仍然崩溃.
如果我在andDo块中添加一个断点,我看到控件到达这一点,并通过getArgument检索正确的对象.

然而,如果我在块中使用getArgument,那么我会尝试做任何事情.

附：感谢帮助.