I don't know if I should have put that in general instead since I think I may not find an answer about it and it will become about everything and nothing but for now let's just start the thread here
Have you ever had a bug where it doesn't seems to make much sense and the temporary solution shouldn't be working in the first place? I just got one of those today.
I was modifying a group of method that required an extra flag for some status. After finishing the task and starting to test it, I had a strange bug where something was going wrong that was not supposed to be affected by the current modification. Since it didn't work, I decided to roll back and to compare the new/old code. Nothing strange was added.
So I decided to remake it step by step, starting first with the simplest modification: increasing the size of a temp buffer by 1. To my surprise, just changing the size created the issue. Puzzled, I decide to create a new variable after the buffer. Same issue. Remove it and put buffer to original size: working. Then I had that strange idea of "let's put a new variable just after that group of zp" and... it's now working. Wth
I cannot be a page boundary bug since it's just a group of zp variables that if I look at the map file, are defined around A0~A9. It just doesn't make sense to just move it and it works.
It may be that I just found a bug where another function is actually using something in that group that it's not supposed or write to something it's not supposed either, maybe, it just that it may take time until I find the cause and was just weird and fun at the same time when I found the cause.
Even if I show how the variables are defined, I don't think there is anything wrong with it so I won't come back on the subject until I dig a little bit more in the code.
Have you ever had one of those strange bugs while writing nes code and the solution didn't make sense either?
Have you ever had a bug where it doesn't seems to make much sense and the temporary solution shouldn't be working in the first place? I just got one of those today.
I was modifying a group of method that required an extra flag for some status. After finishing the task and starting to test it, I had a strange bug where something was going wrong that was not supposed to be affected by the current modification. Since it didn't work, I decided to roll back and to compare the new/old code. Nothing strange was added.
So I decided to remake it step by step, starting first with the simplest modification: increasing the size of a temp buffer by 1. To my surprise, just changing the size created the issue. Puzzled, I decide to create a new variable after the buffer. Same issue. Remove it and put buffer to original size: working. Then I had that strange idea of "let's put a new variable just after that group of zp" and... it's now working. Wth
I cannot be a page boundary bug since it's just a group of zp variables that if I look at the map file, are defined around A0~A9. It just doesn't make sense to just move it and it works.
It may be that I just found a bug where another function is actually using something in that group that it's not supposed or write to something it's not supposed either, maybe, it just that it may take time until I find the cause and was just weird and fun at the same time when I found the cause.
Even if I show how the variables are defined, I don't think there is anything wrong with it so I won't come back on the subject until I dig a little bit more in the code.
Have you ever had one of those strange bugs while writing nes code and the solution didn't make sense either?