Omnimaga

General Discussion => Other Discussions => Miscellaneous => Topic started by: Hot_Dog on February 02, 2011, 11:41:37 pm

Title: Lengthy time to find one ASM error
Post by: Hot_Dog on February 02, 2011, 11:41:37 pm
What's your record time--meaning longest time--for finding a single error (meaning one line of code) in your ASM program, an error that once you fixed everything worked perfectly?  My record was two days for a "pop hl"
Title: Re: Lengthy time to find one ASM error
Post by: DJ Omnimaga on February 03, 2011, 12:01:47 am
Sadly I do not do ASM, but the longest time for any language for me would be five months in Visual Basic 6, but I forgot what was the bug. (It was tilemap-related and one single thing that did not work while the rest worked despite being similar code but I forgot what)
Title: Re: Lengthy time to find one ASM error
Post by: calc84maniac on February 03, 2011, 12:07:15 am
Hmm, I know it took me quite a while to realize that when I added a backbuffer to the old, old Project M (the Mario Bros Classic one), that it was sharing the same space as my object data. But that was back when I coded exclusively oncalc. :P Can't think of anything more recent off the top of my head.
Title: Re: Lengthy time to find one ASM error
Post by: Xeda112358 on February 03, 2011, 12:07:49 am
hahahahahahahahahahahahaha.... um, several months? I forgot to add 23 or inc hl at the beginning. It was why it took me so long to get SpriteLib to be the app BatLib. I forgot that my call ConvDecAtHL required HL to point to the second byte of an FP number.
Title: Re: Lengthy time to find one ASM error
Post by: Deep Toaster on February 03, 2011, 12:33:21 am
Euh, does this count?

I made my first ASM program. It didn't work, so I gave up.

A couple months later, after learning a lot more ASM, I came back to it and fixed it.
Title: Re: Lengthy time to find one ASM error
Post by: JosJuice on February 03, 2011, 01:38:24 am
I couldn't compile the first program I made... I saved it as a txt file instead of asm :P
It took at least an hour to find that...
Title: Re: Lengthy time to find one ASM error
Post by: jnesselr on February 03, 2011, 05:51:15 pm
Me? I spent about half a year or more in a USB code with Apple's iokit (Used to access devices like USB), and couldn't figure out why it showed a device was there, but then stalled and said it wasn't there, but then said it was there again, until I added a like .05 sec pause between writing and reading.