macOS Uncaught exception on only one computer

[davbeck]

I have a program, that runs perfectly fine on my Intel laptop and my G4 iMac. However when I take it over to an Intel iMac, it gives me the following error.

[Session started at 2008-10-20 09:41:15 -0700.]
2008-10-20 09:41:15.893 CSV to SHP[300:10b] An uncaught exception was raised
2008-10-20 09:41:15.894 CSV to SHP[300:10b] *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)
2008-10-20 09:41:15.895 CSV to SHP[300:10b] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)'
2008-10-20 09:41:15.895 CSV to SHP[300:10b] Stack: (
    2473353547,
    2483985979,
    2473353003,
    2473353066,
    2458917823,
    2458383688,
    9888,
    2473412949,
    2501085898,
    2501045494,
    2501043800,
    2501042843,
    2501042649,
    2501041800
)

The Debugger has exited due to signal 5 (SIGTRAP).The Debugger has exited due to signal 5 (SIGTRAP).

this happens weather I use the same compiled executable or try to rebuild it.

 

[Aranince]

I don't know why its happening on one machine but not the others, but what the error means is that a variable has no value, or you're trying to access apart of an array that does not exist. Example, array[0] and array[1] exist, but you are trying access array[2].

 

[kainjow]

Can you post some code? It looks like you're not checking your array bounds properly.

 

[Sayer]

Sounds like my job every day; it works on one Mac, but not another because it is/is not PPC, Intel, 10.5, 10.4 or 10.3.9.

I actually had a bug that only happened on Intel Macs, not PPC, even if they had the same version OS X.

Do all of the Macs have the same version of Mac OS X installed? Maybe the root cause is you are using a function that is not available or behaves differently on the one iMac than the other two macs.

 

[davbeck]

Thanks for the quick reply.
The reason it was only working on my two computers, is because I have been testing on those, and there were some settings already input. the other computers didn't have those settings and, when trying to access them, crashed the program.

Thanks, Aranince, for pointing out the cause of the error.