I was debugging into a subroutine that gets called from a bunch of different places, and it didn't look like the problem was occurring the first time. So I created a global variable to count how many times it had been called. For several hours, I couldn't get the fucking thing to change as I stepped past the ++ code, but I finally managed to remember the necessary esoteria to fix at least *that* part of the problem. It turns out it *is* happening on the first call, but slightly at random, because some ISR the customer is calling somewhere is messing up the stack in mid-subroutine, which is causing an alignment error in the processor.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2008-09-16 02:57 pm (UTC)*smiles and nods*
Date: 2008-09-16 06:07 pm (UTC)Re: *smiles and nods*
Date: 2008-09-16 10:43 pm (UTC)no subject
Date: 2008-09-16 11:46 pm (UTC)but i still knew from the length of the "yeeesss" to be happy for you. :P