Code: Select all
***** Encountered localException during initialisation in [Universe update:] : NSInvalidArgumentException : *** -[NSCFString count]: selector not recognized [self = 0x7227e20] *****
2007-03-25 23:09:22.756 Oolite[230] *** NSTimer discarding exception '*** -[NSCFString count]: selector not recognized [self = 0x7227e20]' that raised during firing of timer with target 115e570 and selector 'doStuff:'
2007-03-25 23:09:22.867 Oolite[230] *** -[NSCFString count]: selector not recognized [self = 0x7227e20]
Oolite [unclassified]:
But what is a fellow supposed to make of this error output (other than sod off, with yer stupid OXP )? I realise this isn't generated by Oolite, but by the graphics layer, by the way
But.... what have I done wrong?
I work in software... I always say: software should never output hexadecimal numbers in its error reports, if it does, there's something wrong with the software, not the error. (Witness: all Microsoft software outputs hexadecimal nubers in its errors... all the time... usually the exact hexadecimal reference to the location in memory, where the error ocurred: veeeery useful, thanks! I rest my case.)
This is not so much a "What's gone wrong this time, then" request, since I know it's of my own doing, but more of a "can we have a proper crash-dump" type request, please? I'm sure this will form part of the major overhaul that Ahruman is doing, but part of the reason I gave up OXPing, earlier was that OXPs, traditionally, failed without giving any useful feed back as to why.