Sometimes in our daily course of debugging@work we get strange issues. I work for a team which debugs Anamolous Mobile Handset behaviour. Many of the times these are in software and we are able to pin point them accurately to the last instruction which faulted.
Also hardware happens to be the culprit sometimes. But there happen to be some cases which are kind of un-explained in software. Such as a mov instruction leading to software reset.
Normally we hit the Software angle first & considerable hours spent in debugging from a purely software perspective is invested. Then we try to examine the hardware. And if we still draw a blank that is the time we are in a dilemma. Recently i saw one issue where the ARM Processor program counter became zero all of a sudden. How this could happen in the circumstances the handset was executing is still a Mystery. While I was caught in the The Yin and Yang I chanced upon some old bug which was due to bad SDRAM read/writes. Well to detect such faults is a big pain in the neck(believe me).
And to say for certain that the above issue is due to faulty read/write requires an efficient debug mechanism which is rarely present with us. Thus some issues intrigue us no end. However I am still debugging the above said bug. Lets see whether its the Yin or the Yang ;-)
~P
No comments:
Post a Comment