Reminded me of the situation in which I was given 'a very peculiar issue which was very hard to simulate' (acc to the description). Considering that it was rela

Reminded me of the situation in which I was given 'a very peculiar issue which was very hard to simulate' (acc to the description). Considering that it was related to the message queue generation module of a core banking system, and that being a production issue, the scene was intense. Almost everyone was convinced that the issue was due to a recent patch to the MQ module but couldn't figure out the reason. On a hunch, after seeing the pattern of errors in the debug logs, I dug up the old link list handler routines in our codebase, and lo and behold, there was an OBOE [1], a very latent one that too, dating back to early 90s. The fix was just an addition of a '=' which got things back on track. That incident made me the official schroedinbug [2] mangler of the unit, causing me to spend countless night-outs thereafter. [1] http://en.wikipedia.org/wiki/Off-by-one_error http://en.wikipedia.org/wiki/Off-by-one_error [2] http://www.catb.org/jargon/html/S/schroedinbug.html http://www.catb.org/jargon/html/S/schroedinbug.html