What is my problem?
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
It's called 'Mystic Debugging'. You'll be asked to join the cast of 'Heroes'
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
Everything has bugs no matter how hard you work on it. Just write a code to restart your machine every 100 hours .... lmao ;)
"I do not know with what weapons World War 3 will be fought, but World War 4 will be fought with sticks and stones." Einstein "Few things are harder to put up with than the annoyance of a good example." Mark Twain
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
Seriously, it happens to all of us, especially with problems that are not easily reproducible. If you have bugs that occur all the time, you just go in and fix them, re-start the bloody thing, and Bob's your uncle. What you do is not fixing bugs. You' are doing a number of changes at the same time, the combination of which eliminate the conditions that caused the bug in the first place. Very nice to keep the machines running, but the bug is probably still there, awaiting the right conditions to rear it's ugly head. You want to read up on Root Cause Analysis. A first step in definitively solving intermittent bugs is usually finding a way to reproduce it reliably. This can be pain-staking process. Once you can reproduce it reliably, you can usually instrument your system so that can you debug it, even with traces and dumps and whatnot before the bugs happens. All tools that you don't have available when the production crashes.
modified on Thursday, April 29, 2010 6:45 AM
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
You must be very intuitive. :) I could be talking rubbish, but are you by any chance left-handed? Left handers are supposedly better at non-linear processing.
Cheers, Vikram. (Got my troika of CCCs!)
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
If it was some sort of memory corruption you probably didn't fix the bug, you just moved it somewhere else. tick tick tick...
-
Seriously, it happens to all of us, especially with problems that are not easily reproducible. If you have bugs that occur all the time, you just go in and fix them, re-start the bloody thing, and Bob's your uncle. What you do is not fixing bugs. You' are doing a number of changes at the same time, the combination of which eliminate the conditions that caused the bug in the first place. Very nice to keep the machines running, but the bug is probably still there, awaiting the right conditions to rear it's ugly head. You want to read up on Root Cause Analysis. A first step in definitively solving intermittent bugs is usually finding a way to reproduce it reliably. This can be pain-staking process. Once you can reproduce it reliably, you can usually instrument your system so that can you debug it, even with traces and dumps and whatnot before the bugs happens. All tools that you don't have available when the production crashes.
modified on Thursday, April 29, 2010 6:45 AM
-
You must be very intuitive. :) I could be talking rubbish, but are you by any chance left-handed? Left handers are supposedly better at non-linear processing.
Cheers, Vikram. (Got my troika of CCCs!)
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.
I once had to send in an official report after "fixing" a tracking problem at a satellite station. "Disconnected one of the blue wires." That was it. Our docs were such that we couldn't figure out what that particular blue wire was for or, for that matter, what the other hundred or so blue wires were for. But disconnecting that particular one did the trick. Not a shining moment, but fun nonetheless.
-
At work it so happens that I fix quite challenging problems(typical non reproducible bugs which occur every hundred hours) but I cannot make out which fix exactly worked. It has happened twice till now. If I undo my fixes bug is reproducible. So definitely there is a fix in my version. Although my manager is impressed but I struggle to explain him and peers what fixed the issue. Most of the times I do know what fix worked but there are some times when I really dont think there is a logical connection with the symptons and my fixes but it works. huh I am going mad.