Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1048825
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T16:31:08+00:00 2026-05-16T16:31:08+00:00

I decided to get back to Cocoa/Objective-C programming recently and my current project calls

  • 0

I decided to get back to Cocoa/Objective-C programming recently and my current project calls for an NSTableView.

I thought I had gotten the process down to a Science but it appears I was wrong. I am getting an EXE_BAD_ACCESS error in the datasource method that actually returns the data.

When I run the application, all results show up on the NSTableView but shortly after, the EXE_BAD_ACCESS occurs. Occasionally, and seemingly randomly, the EXE_BAD_ACCESS error will not be thrown and instead I will get various errors in the console like the one below:

-[NSCFString objectAtIndex:]: unrecognized selector sent to instance 0x10011b780

Afterwards, the interface becomes mostly unresponsive.

From various debug messages I have been able to predict that an error is occurring because the method is being called with a row integer that is greater than the data NSArray’s count. Is my Mac screwing up or am I doing something wrong?

Below is my code:

Header File (TableViewController.h)

#import <Cocoa/Cocoa.h>


@interface TableViewController : NSObject {
    IBOutlet NSTableView *tableView;

    NSArray *componentArray;
}

@end

Main File (TableViewController.m)

#import "TableViewController.h"


@implementation TableViewController

- (void) awakeFromNib {
    NSString *components = @"Test:Test2:Test3";
    componentArray = [components componentsSeparatedByString:@":"];

    [tableView setDataSource:self];
    [tableView reloadData];
}

- (int)numberOfRowsInTableView:(NSTableView *)tableView {
    return [componentArray count];
}

- (id)tableView:(NSTableView *)tableView objectValueForTableColumn:(NSTableColumn *)tableColumn row:(int)row {
    // EXE_BAD_ACCESS is occuring here
    return [componentArray objectAtIndex:row];
}

@end
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T16:31:08+00:00Added an answer on May 16, 2026 at 4:31 pm
    componentArray = [components componentsSeparatedByString:@":"];
    

    The -componentsSeparatedByString: method returns an -autoreleased array. Therefore, by the time it is needed, the componentArray may no longer be valid.

    You need to -retain it explicitly.

    componentArray = [[components componentsSeparatedByString:@":"] retain];
    

    (of course, make sure to -release the array in -dealloc. Or just turn on Garbage Collection and forget about memory management.)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.