Author Topic: Bug Reports (Read 455739 times)

DJ Omnimaga · « **Reply #330 on:** June 12, 2010, 01:11:16 pm »

mhmm weird, it doesn't work for me either. It's almost like if Quigibo accidentally removed this feature totally in Axe 0.2.6 or something

. He will have to check this too I guess :S

Welcome here by the way

Ikkerens · « **Reply #331 on:** June 12, 2010, 01:19:20 pm »

Quote from: DJ Omnimaga on June 12, 2010, 01:11:16 pm

mhmm weird, it doesn't work for me either. It's almost like if Quigibo accidentally removed this feature totally in Axe 0.2.6 or something . He will have to check this too I guess :S

Welcome here by the way

Thanks, have been around for a while here, only created my account today.

DJ Omnimaga · « **Reply #332 on:** June 12, 2010, 01:20:21 pm »

Aaaah ok ^^

I hope you stay interested in programming those little machines for a while ^^

Ikkerens · « **Reply #333 on:** June 12, 2010, 01:31:20 pm »

Quote from: DJ Omnimaga on June 12, 2010, 01:20:21 pm

Aaaah ok ^^

I hope you stay interested in programming those little machines for a while ^^

I will most likely as long as im on high school

Deep Toaster · « **Reply #334 on:** June 12, 2010, 09:22:19 pm »

Quote from: Quigibo on June 09, 2010, 01:08:21 am

@Deep Thought, that sounds too strange to be an internal error. Something must have gotten overridden. I think a ram clear would be a sufficient fix but I don't know.

I'd like to request that from now on, please give your calculator type and OS version when reporting any major bugs. This is becasue I am adding a lot of calculator specific stuff next version. Also but from 0.3.0 on, when you receive an unexpected error "ERR: UNKNOWN" it will also give a 7 digit code that I can use to find where and when the error occurred.

Here's another similarly weird error: I compile a 400-byte program, which worked pretty well before, but now, when I run it from MirageOS, it has some weird glitches. I look in the source to find why it led to those glitches, and I find that Axe somehow modified one token in the source from a 0 to some undisplayable character (designated by ?). This happened again a few compiles later, but this time it changed some token (I don't remember which one, but it might have been If into something like sin^-1(. The second time happened after a (purposeful) RAM clear, so it wasn't a buggy program.

Thinking a GarbageCollect would do the trick, as it did in my previous error post, I went into the Catalog, then selected Garbage Collect. After it copied it to the screen, I pressed ENTER to run it, as always. But this time, it didn't actually run. In fact, it didn't even display the Garbage Collect? message. The calculator just froze. It wasn't even a normal freeze, where the run indicator seems to be stuck in its spinning mode. This time, the run indicator seemed to be frozen in the Pause mode (with the alternating dots). The calculator was fixed when I removed a battery (resetting the RAM in the process, of course).

Quigibo · « **Reply #335 on:** June 12, 2010, 09:36:19 pm »

Okay, I think I might know what the problem is. Can those who had problems confirm this:

Were your executables archived prior to compiling a new build of the program? I think becasue the app has to delete the archived programs so often it causes the OS to mess up the rom somehow which causes other problems. I might have to have Axe automatically garbage collect or something to solve this. That would also explain why most people who are getting this error are using shells, becasue you can run the programs when they're archived.

Runer112 · « **Reply #336 on:** June 12, 2010, 09:39:16 pm »

I could've told you that before Quigibo

I've always been compiling my programs from RAM because I noticed that they get random errors when compiling from Flash.

calc84maniac · « **Reply #337 on:** June 12, 2010, 09:40:47 pm »

Quote from: Quigibo on June 12, 2010, 09:36:19 pm

Okay, I think I might know what the problem is. Can those who had problems confirm this:

Were your executables archived prior to compiling a new build of the program? I think becasue the app has to delete the archived programs so often it causes the OS to mess up the rom somehow which causes other problems. I might have to have Axe automatically garbage collect or something to solve this. That would also explain why most people who are getting this error are using shells, becasue you can run the programs when they're archived.

No, that can't be the issue. The OS knows what it's doing when it messes with archive.

Quigibo · « **Reply #338 on:** June 12, 2010, 09:49:05 pm »

I don't understand how that's possible. I'm only using OS bcalls when writing to rom and as Deep Thought stated, its not an issue with any part of the RAM since it continues after a ram clear it has to be somewhere in rom.

@Runner12
You're getting errors with the source or previous executable in archive? What errors and where would it scroll?

Runer112 · « **Reply #339 on:** June 12, 2010, 09:50:03 pm »

Random.

For example, I loaded my sprite editor source (I assume it's some sort of reading problem, so a bigger source, in this case almost 15KB, probably means more probability for errors) into archive and compiled it five times, here are the results:

67% - ERR: LBL MISSING (and on the first pass?)
78% - ERR: BAD SYMBOL
Success
89% - ERR: DUPLICATE
Success

Quigibo · « **Reply #340 on:** June 12, 2010, 09:55:50 pm »

Wait, is this replicate-able? Can you post the source that does this?

Runer112 · « **Reply #341 on:** June 12, 2010, 09:57:35 pm »

What do you mean? You can't really replicate it because it's random.

calc84maniac · « **Reply #342 on:** June 12, 2010, 09:59:59 pm »

Quote from: Runer112 on June 12, 2010, 09:57:35 pm

What do you mean? You can't really replicate it because it's random.

Failed 3 out of 5 times, sounds pretty replicate-able.

Deep Toaster · « **Reply #343 on:** June 12, 2010, 10:05:41 pm »

Quote from: Quigibo on June 12, 2010, 09:36:19 pm

Okay, I think I might know what the problem is. Can those who had problems confirm this:

Were your executables archived prior to compiling a new build of the program? I think becasue the app has to delete the archived programs so often it causes the OS to mess up the rom somehow which causes other problems. I might have to have Axe automatically garbage collect or something to solve this. That would also explain why most people who are getting this error are using shells, becasue you can run the programs when they're archived.

Thanks, I remember now. Those were two of the rare times I compiled out of Archive.

Do you know why it messes up archived programs, though? Would it be possible for a future version of Axe to fix the bug?

Runer112 · « **Reply #344 on:** June 12, 2010, 10:06:43 pm »

http://ourl.ca/4832/94254

Author Topic: Bug Reports (Read 455739 times)

DJ Omnimaga

Re: Bug Reports

Ikkerens

Re: Bug Reports

DJ Omnimaga

Re: Bug Reports

Ikkerens

Re: Bug Reports

Deep Toaster

Re: Bug Reports

Quigibo

Re: Bug Reports

Runer112

Re: Bug Reports

calc84maniac

Re: Bug Reports

Quigibo

Re: Bug Reports

Runer112

Re: Bug Reports

Quigibo

Re: Bug Reports

Runer112

Re: Bug Reports

calc84maniac

Re: Bug Reports

Deep Toaster

Re: Bug Reports

Runer112

Re: Bug Reports