« previous next »
Pages: 1 ... 124 125 [126] 127 128 ... 133   Go Down

Author Topic: Bug Reports  (Read 464950 times)

0 Members and 1 Guest are viewing this topic.

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1875 on: November 13, 2013, 01:31:22 pm »
Quote from: Matrefeytontias on November 13, 2013, 03:46:07 am
Another bug with Axe 1.2.2 : it seems that you forgot to check whether we compile as  an app or not before saying "APP TOO BIG". I want to compile a 16464 bytes MirageOS program, but it won't do.

1097E710AFA74E43
A668A668DB990012
0B378B810011FF00
040A406D4AD14976

Sorry, fixed!

Also, I probably should've gotten into this habit a while ago, but I'm going to make my development builds publicly available. That way, if I made a silly bug like this and fixed it really easily, but haven't made enough changes to warrant a new release version of Axe, you can still get the bug fix. Also, if anyone requests a feature and I implement it, they can test it out as soon as I'm done coding it.

Ideally, this should be the link for this and all future development builds, at least of the Axe 1.x line:

https://dl.dropboxusercontent.com/u/34812306/Axe.8xk
« Last Edit: November 13, 2013, 01:32:21 pm by Runer112 »
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1876 on: November 18, 2013, 01:21:51 pm »
Another bug with the version you just posted (and the previous one too) : if I compile a program that has an invalid name (lowercases in it for example), it says ERR:INVALID NAME or w/e (I don't remember exactly), as expected, but then it enters the program, and after 15 seconds or so, it starts scrolling until it reaches the end. That's particularly annoying with a 7k source.
« Last Edit: November 18, 2013, 01:22:24 pm by Matrefeytontias »
Logged

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1877 on: November 18, 2013, 02:58:21 pm »
I've tried to replicate that with a few different sources, including a large one that spans two flash pages, which has caused error scrolling issues in the past, but I couldn't recreate the bug you're describing. Do you think there are any other details you could provide to narrow down the cause?
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1878 on: November 18, 2013, 03:31:12 pm »
Hum, the source was not archived and the name was IkarugaX with a space and more chars. But that's all that was noticeable.
Logged

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1879 on: November 18, 2013, 03:41:38 pm »
I tried changing the target name in the header of a random large source to IkarugaX and added a description, but everything still seemed fine.

EDIT: Nevermind, I replicated it. Trying to solve now.
« Last Edit: November 18, 2013, 03:44:25 pm by Runer112 »
Logged

Offline Xeda112358

  • they/them
  • Moderator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 4704
  • Rating: +719/-6
  • Calc-u-lator, do doo doo do do do.
    • View Profile
Re: Bug Reports
« Reply #1880 on: February 08, 2014, 04:18:24 pm »
Do you know if Axe will ever be able to work in WabbitEmu and jsTIfied again? It always crashes for me.
Logged

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1881 on: February 08, 2014, 04:36:14 pm »
Sounds like your ROM might have been infected by bootfree. I believe some versions of Wabbitemu decided to randomly splice the third-party bootfree boot code into ROMs, which breaks flash unlocks designed for the real TI boot code, which Axe relies on. I'd recommend updating Wabbitemu to the latest version, which I believe shouldn't unexpectedly do this, and trying to replace your ROM file with a fresh one from your physical calculator.
« Last Edit: February 08, 2014, 04:44:18 pm by Runer112 »
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1882 on: February 16, 2014, 03:35:51 pm »
Not really a bug, but you apparently forgot to update the latest Axe.inc : a quick disassembly shows that axv_r1 is actually $9109 and not $9D31 like the file says. I didn't check for other variables.
Logged

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1883 on: February 16, 2014, 03:38:55 pm »
Oops, looks like basically every variable has the wrong location defined... I've made a note to fix that later, as it doesn't seem to be a bug that requires immediate fixing.
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1884 on: February 17, 2014, 06:30:51 am »
In my axiom again, I have this :
Code: [Select]
axiom1:
  call sub_axiom2
...
axiom2:
 call sub_axiom3 ; several non-consecutive times
...
axiom3:
 ...With that, Axe compiles fine when it encounters the #Axiom line and even the axiom1( command, but it says "Invalid axiom" when the first pass is fully completed. Besides, when I put axiom3 inside axiom2 as a relative call, everything works fine. De hell ?
Logged

Offline Runer112

  • Project Author
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2289
  • Rating: +639/-31
    • View Profile
Re: Bug Reports
« Reply #1885 on: February 17, 2014, 09:08:23 am »
I don't think that gives me quite enough information to know what's going on. Can you provide the Axiom itself, and perhaps a source program that includes it which triggers the compile error?
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1886 on: February 18, 2014, 01:42:23 pm »
Sent by PM.
Logged

Offline Matrefeytontias

  • Axe roxxor (kinda)
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1982
  • Rating: +310/-12
  • Axe roxxor
    • View Profile
    • RMV Pixel Engineers
Re: Bug Reports
« Reply #1887 on: March 04, 2014, 06:53:08 am »
Bump,

Bitmap(X,Y,Pic,Buffer,Mode) somehow doesn't seem to work with MirageOS. Either that or FullRene. Here is my code :

:[0E0EFFFC800480048004800480048004800480048004800480048004FFFC→Pic9
:While 1
:. Don't worry it's meant
:Bitmap(r1*16+17→r3,r2*14+4→r4,Pic9,L6,1)
:DispGraphrr
:Bitmap(r3,r4,Pic9,L6,1)
:!If r6++^8
:getKey(3)-getKey(2)+r1^4→r1
:getKey(1)-getKey(4)+r2^4→r2
:End
:EndIf getKey(9)

When that runs, the displayed imaged is all wonky. Also, it's compiled for Ion, although ran with MirageOS.

EDIT : note that this is in the middle of a bigger code, which compiled is >8300 bytes.
« Last Edit: March 04, 2014, 07:03:09 am by Matrefeytontias »
Logged

Offline n141421

  • LV0 Newcomer (Next: 5)
  • Posts: 1
  • Rating: +0/-0
    • View Profile
Re: Bug Reports
« Reply #1888 on: April 12, 2014, 01:49:00 pm »
I found three Axe 1.2.2 bugs :
  • 1+{Y1} is equal to {Y1}, whereas {Y1}+1 works correctly. Actually, everything before a file read is not taken in account, as if HL was reset.
  • The *^ operator gives strange results, like 1000*^1 = 775. It didn't happen with Axe 1.2.1.
  • When a Return is at the last line of a source file, it is ignored. For example, "2:Return 1" returns 2, but "2:Return 1:" returns 1.
Logged

Offline Sorunome

  • Fox Fox Fox Fox Fox Fox Fox!
  • Support Staff
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 7920
  • Rating: +374/-13
  • Derpy Hooves
    • View Profile
    • My website! (You might lose the game)
Re: Bug Reports
« Reply #1889 on: April 25, 2014, 11:16:59 am »
Uh, very weird bug in 1.2.2a:
(This is only on one of my TI-83+SE's)
First, when starting to compile it insta-ram-clears
then, after starting some other apps, it compiles. I tried an APP.
After Defragmenting I get ERR:MEMORY, only with the option 1:Quit, so i hit it, and now I'm stuck in an infinity loop of ERR:LINK (Also only giving me the option to quit)
After pulling the battery (and a ram clear due to that) it already craches when I enter the 'Compile' menu.
Is it the calculator that is acting up? :P
Self test said everything was fine but that one only checkes the RAM iirc, so IDK.....
And yes, i tried re-sending axe.

EDIT: Ok, that actually might be the calculator because it randomley ram clears on starting zstart
« Last Edit: April 25, 2014, 11:21:10 am by Sorunome »
Logged

THE GAME
Also, check out my website
If OmnomIRC is screwed up, blame me!
Click here to give me an internet!
Pages: 1 ... 124 125 [126] 127 128 ... 133   Go Up
« previous next »