Debugging , art or sience ?
-
Hi there, (excuse my english ... not my native language ;-) I am actually wondering about what "debugging" is , and how ones generally proceed in this task. I've been googling to find some 'theorical' articles, or 'bug taxonomy'(*) , or 'debugging strategy', or more general reflexion on the subject. The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem. I think "debugging" is an important activity since it could take a long time , and have a big economical impact, and on the other end it does not seems to be studied in a pragmatic point of view (... I am not speaking of a kind of a "matematical theory of debugging" ... finite state machine ... and so ...) If anyone here has links to a really "theoricall" aproach of debugging I'll much apreciate !! (*) I mean in the IT field ;-) Thanks in advance Marc
-
Hi there, (excuse my english ... not my native language ;-) I am actually wondering about what "debugging" is , and how ones generally proceed in this task. I've been googling to find some 'theorical' articles, or 'bug taxonomy'(*) , or 'debugging strategy', or more general reflexion on the subject. The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem. I think "debugging" is an important activity since it could take a long time , and have a big economical impact, and on the other end it does not seems to be studied in a pragmatic point of view (... I am not speaking of a kind of a "matematical theory of debugging" ... finite state machine ... and so ...) If anyone here has links to a really "theoricall" aproach of debugging I'll much apreciate !! (*) I mean in the IT field ;-) Thanks in advance Marc
-
Hi there, (excuse my english ... not my native language ;-) I am actually wondering about what "debugging" is , and how ones generally proceed in this task. I've been googling to find some 'theorical' articles, or 'bug taxonomy'(*) , or 'debugging strategy', or more general reflexion on the subject. The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem. I think "debugging" is an important activity since it could take a long time , and have a big economical impact, and on the other end it does not seems to be studied in a pragmatic point of view (... I am not speaking of a kind of a "matematical theory of debugging" ... finite state machine ... and so ...) If anyone here has links to a really "theoricall" aproach of debugging I'll much apreciate !! (*) I mean in the IT field ;-) Thanks in advance Marc
What is "debugging"?[^] Both, art and science.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
-
What is "debugging"?[^] Both, art and science.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Thanks for paying attention to my post did I mention that "The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem." ... oh yes I did... :) Marc
-
Thanks for paying attention to my post did I mention that "The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem." ... oh yes I did... :) Marc
Well then, you've asked the wrong question. The problem is not that you reached the limit of a search engine, but that you reached the limit of yourself to formulate the correct question to get what you want. Like the search engines, I have no idea what you want know. There is no site dedicated to all things "debugging". No one article or set of articles that covers all aspects of it. It's simply the hundreds, if not thousands, of processes and techniques used to find problems in code. No single, or small set of sources is going to cover all that.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Well then, you've asked the wrong question. The problem is not that you reached the limit of a search engine, but that you reached the limit of yourself to formulate the correct question to get what you want. Like the search engines, I have no idea what you want know. There is no site dedicated to all things "debugging". No one article or set of articles that covers all aspects of it. It's simply the hundreds, if not thousands, of processes and techniques used to find problems in code. No single, or small set of sources is going to cover all that.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
hummm... well I just wanted to know if anyone here has links to a really "theoricall" aproach of debugging. and didn't find anything deep enough through the search engine. Just as simple, cant make it clearer sorry. Marc
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Hi there, (excuse my english ... not my native language ;-) I am actually wondering about what "debugging" is , and how ones generally proceed in this task. I've been googling to find some 'theorical' articles, or 'bug taxonomy'(*) , or 'debugging strategy', or more general reflexion on the subject. The problem is that in such case you reach the limit of the search engine : answers are crowded about specific bugs for specific language , and the few articles (Wikipedia) were just at the 'surface' of the problem. I think "debugging" is an important activity since it could take a long time , and have a big economical impact, and on the other end it does not seems to be studied in a pragmatic point of view (... I am not speaking of a kind of a "matematical theory of debugging" ... finite state machine ... and so ...) If anyone here has links to a really "theoricall" aproach of debugging I'll much apreciate !! (*) I mean in the IT field ;-) Thanks in advance Marc
I have a highly theoretically approach to debugging, it goes something like this: "I don't write any bugs, and anyone who says otherwise is a double-damned liar not to be trusted" :D In all seriousness, I think it depends where in the application cycle you are, and what your actually involvement with the application is. For example, if this is a new application that you're developing you might want to take a look at some of the techniques available for developing robust code. In particular I'm thinking about Unit Testing - Marc Clifton of this parish has written loads about this, have a look at his site here: http://www.marcclifton.com/[^] If the application is already out in the wild, then you're a little bit more limited in that a) you generally respond to issues raised by the users b) depending on who put the application together, you may not have access to all the design information you need. In this sense, it's a bit more hit and miss.