Author Topic: Bug Reports  (Read 408093 times)

0 Members and 2 Guests are viewing this topic.

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: Bug Reports
« Reply #765 on: September 17, 2010, 07:16:46 pm »
Maybe it's the smaller archive space? I had that problem after compiling too many prgms, and a GarbageCollect worked fine.




Offline Michael_Lee

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1019
  • Rating: +124/-9
    • View Profile
Re: Bug Reports
« Reply #766 on: September 18, 2010, 10:18:24 am »
Yes - garbage collecting seems to work wonders.  I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.
My website: Currently boring.

Projects:
Axe Interpreter
   > Core: Done
   > Memory: Need write code to add constants.
   > Graphics: Rewritten.  Needs to integrate sprites with constants.
   > IO: GetKey done.  Need to add mostly homescreen IO stuff.
Croquette:
   > Stomping bugs
   > Internet version: On hold until I can make my website less boring/broken.

Offline calcdude84se

  • Needs Motivation
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2272
  • Rating: +78/-13
  • Wondering where their free time went...
    • View Profile
Re: Bug Reports
« Reply #767 on: September 19, 2010, 02:46:32 pm »
Code: [Select]
input acts funnily...
prgmBASIC
[code=BASIC]Input "THE GAME: ",A
prgmAXE when compiled
Code: (Axe) [Select]
inputRunning these two programs in the order given, My screen will look like this:
prgmBASIC
THE GAME: 1337
            Done
Asm(prgmAXE
THE GAME:

In addition, pressing 2nd+Quit will quit the program, causing memory leaks, and it may be the same for 2nd+Off (haven't tried yet)[/code]
Edit: Weird formatting errors. Can't fix.
« Last Edit: September 19, 2010, 02:51:21 pm by calcdude84se »
"People think computers will keep them from making mistakes. They're wrong. With computers you make mistakes faster."
-Adam Osborne
Spoiler For "PartesOS links":
I'll put it online when it does something.

Offline Builderboy

  • Physics Guru
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5673
  • Rating: +613/-9
  • Would you kindly?
    • View Profile
Re: Bug Reports
« Reply #768 on: September 19, 2010, 03:33:18 pm »
I think this has been reported already?  Surely there has been many a but with the input command and stuff before it x.x seems like a common bug

Offline calcdude84se

  • Needs Motivation
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2272
  • Rating: +78/-13
  • Wondering where their free time went...
    • View Profile
Re: Bug Reports
« Reply #769 on: September 19, 2010, 03:35:35 pm »
I'm not sure, it might have been.
At any rate I'm bumping it ;D
"People think computers will keep them from making mistakes. They're wrong. With computers you make mistakes faster."
-Adam Osborne
Spoiler For "PartesOS links":
I'll put it online when it does something.

Offline ztrumpet

  • The Rarely Active One
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5712
  • Rating: +364/-4
  • If you see this, send me a PM. Just for fun.
    • View Profile
Re: Bug Reports
« Reply #770 on: September 19, 2010, 05:19:27 pm »
The input bug seems pretty glitchy. =/

Offline Quigibo

  • The Executioner
  • CoT Emeritus
  • LV11 Super Veteran (Next: 3000)
  • *
  • Posts: 2031
  • Rating: +1075/-24
  • I wish real life had a "Save" and "Load" button...
    • View Profile
Re: Bug Reports
« Reply #771 on: September 19, 2010, 05:54:16 pm »
Well apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it.  I will have to find the name of that string.  The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.

There isn't a way to fix the memory leaks since this is an OS call.
« Last Edit: September 19, 2010, 05:56:11 pm by Quigibo »
___Axe_Parser___
Today the calculator, tomorrow the world!

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55942
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Bug Reports
« Reply #772 on: September 19, 2010, 11:54:42 pm »
Are the mem leaks TI fault? It might be best to use a different input routine then if it can cause issues during game run time x.x (although I guess that might produce larger executables, rigth?). Good luck with the current input routine for now, though.
Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: Bug Reports
« Reply #773 on: September 20, 2010, 10:56:33 am »
Quote from: Michael_Lee
Yes - garbage collecting seems to work wonders.  I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.

But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.




Offline kindermoumoute

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 836
  • Rating: +54/-3
    • View Profile
Re: Bug Reports
« Reply #774 on: September 20, 2010, 01:00:31 pm »
And how to use axe input command? (i search, and always much crash)
Projects :

Worms armageddon z80 :
- smoothscrolling Pixelmapping : 100%
- Map editor : 80%
- Game System : 0%

Tutoriel français sur l'Axe Parser
- 1ère partie : en ligne.
- 2ème partie : en ligne.
- 3ème partie : en ligne.
- 4ème partie : 10%
- Annexe : 100%

Offline Michael_Lee

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1019
  • Rating: +124/-9
    • View Profile
Re: Bug Reports
« Reply #775 on: September 20, 2010, 01:57:54 pm »
Quote from: Michael_Lee
Yes - garbage collecting seems to work wonders.  I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.

But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.

I doubt it.  The 'mysterious errors' usually only occur after I try running a normal, tested program after doing something incredibly stupid with my calculator.  (As in, I mess up with pointers and accidentally write a bunch of data to random places).  It's probably not Axe's fault.
My website: Currently boring.

Projects:
Axe Interpreter
   > Core: Done
   > Memory: Need write code to add constants.
   > Graphics: Rewritten.  Needs to integrate sprites with constants.
   > IO: GetKey done.  Need to add mostly homescreen IO stuff.
Croquette:
   > Stomping bugs
   > Internet version: On hold until I can make my website less boring/broken.

Offline calcdude84se

  • Needs Motivation
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2272
  • Rating: +78/-13
  • Wondering where their free time went...
    • View Profile
Re: Bug Reports
« Reply #776 on: September 20, 2010, 09:13:18 pm »
Well apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it.  I will have to find the name of that string.  The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.

There isn't a way to fix the memory leaks since this is an OS call.
As you are probably aware, there is a leak-free (or less so) version of _GetKey, undocumented and called _GetKeyRetOff ;D
I wonder if something similar exists for the input bcall...
Good luck making it work! :)
« Last Edit: September 20, 2010, 09:13:39 pm by calcdude84se »
"People think computers will keep them from making mistakes. They're wrong. With computers you make mistakes faster."
-Adam Osborne
Spoiler For "PartesOS links":
I'll put it online when it does something.

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: Bug Reports
« Reply #777 on: September 21, 2010, 07:44:17 pm »
Quote from: Michael_Lee
Yes - garbage collecting seems to work wonders.  I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.

But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.

I doubt it.  The 'mysterious errors' usually only occur after I try running a normal, tested program after doing something incredibly stupid with my calculator.  (As in, I mess up with pointers and accidentally write a bunch of data to random places).  It's probably not Axe's fault.

Ah. Yeah, I accidentally do that pretty often, giving me random tokens in the middle of my program :D




Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55942
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Bug Reports
« Reply #778 on: September 22, 2010, 12:07:39 pm »
Well apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it.  I will have to find the name of that string.  The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.

There isn't a way to fix the memory leaks since this is an OS call.
As you are probably aware, there is a leak-free (or less so) version of _GetKey, undocumented and called _GetKeyRetOff ;D
I wonder if something similar exists for the input bcall...
Good luck making it work! :)
If it's undocumented, does it means it won't work on the Nspire, though? I think Quigibo is aiming for full Nspire compatibility with the exception of the Full command.

Quote from: Michael_Lee
Yes - garbage collecting seems to work wonders.  I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.

But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.

I doubt it.  The 'mysterious errors' usually only occur after I try running a normal, tested program after doing something incredibly stupid with my calculator.  (As in, I mess up with pointers and accidentally write a bunch of data to random places).  It's probably not Axe's fault.

Ah. Yeah, I accidentally do that pretty often, giving me random tokens in the middle of my program :D
Yeah this is why it's better to reset every now and then x.x
Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

Offline kindermoumoute

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 836
  • Rating: +54/-3
    • View Profile
Re: Bug Reports
« Reply #779 on: September 22, 2010, 12:33:51 pm »
Please, how to use input command?
(I've so many crash, help me)
Projects :

Worms armageddon z80 :
- smoothscrolling Pixelmapping : 100%
- Map editor : 80%
- Game System : 0%

Tutoriel français sur l'Axe Parser
- 1ère partie : en ligne.
- 2ème partie : en ligne.
- 3ème partie : en ligne.
- 4ème partie : 10%
- Annexe : 100%