Omnimaga
Calculator Community => Major Community Projects => The Axe Parser Project => Topic started by: Mighty Moose on February 09, 2011, 10:35:28 pm
-
I got this after compiling and running an axe program. Any ideas what it is?
-
Never gotten it... Do you know what program you were compiling when you got that?
-
A secret project I have been working on...
I'll try to make a screenie...
EDIT: Not a GIF (Wabbit doesn't want to reproduce...), but here, from TIScreenCapture:
-
Wait, it's during compilation? That's weird...
I want to say your flash is corrupted, but there's probably a better explanation. Last time I corrupted my archive, though, I hit an error that was something like ERR:$#$@LlAVJSJfajdlvADSFI38234... (Random junk, you get the point.)
-
I thought ? was for an undefined error. Or is that something else.
-
Maybe when there's an undefined error, it displays a string at some random point in memory. That would explain the random junk in my error.
-
Not totally sure how this would apply, but I've gotten that error before. It was due to some faulty input to a _ChkFindSym romcall. Not sure what else could trigger that error, but the TI-OS does have error checking for strange things like that.
-
Yeah I would guess its something corrupted in the symbol table. If you haven't already, I would recommend a data backup and ram clear and see if that works. If you happened to archive anything while the symbol table was corrupted, it could have resulted in the archive's entry also getting corrupted in which case you would have to do a full rom clear.
-
So, this is even worse than UNKNOWN? But it seems to be a client thing.
Mighty Moose, please save the code and then when you can share it, please do so we can check if it is a client thing or a general problem.
-
This is not while compiling, but running.
I backed up the offensive program (and most of my other stuff on calc), but the error mysteriously disappeared after trying to reproduce it...
I will try to reproduce it again (it just crashed my 84+ when I ran it on that one).
Of course, in a previous compiling of the program (with less modified source code) I kept getting a bunch of ERR:BREAKs without pressing any keys. ???
-
It sounds to me like this piece of code is doing something it really shouldn't be. You can get all sorts of weird errors when writing over parts of the calc that it doesn't like, are you checking to make sure your pointers are pointing to where you think they are pointing?