Level: 10k+ Postman
Joined: Fri. Jul 1, 2005
Posts: 15419 View posts
Location: Basingstoke, Hampshire, UK
The 6 Stages of Debugging
Author
Message
Those are common replies to OP's around here...............
JIm
If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman
Please Read: Code-of-Conduct
Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user
Level: 10k+ Postman
Joined: Fri. Jul 1, 2005
Posts: 15419 View posts
Location: Basingstoke, Hampshire, UK
exactly!
In my work I often add
7. How could I have been so stupid?!
kk6gm wrote:
In my work I often add
7. How could I have been so stupid?!
+1
Jim
If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman
Please Read: Code-of-Conduct
Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user
after a few months....
#8 Is that happening AGAIN???
avrcandies wrote:
Immediately followed by, "DRAT! What was it I did to fix this the last time?"#8 Is that happening AGAIN???
frog_jr wrote:
avrcandies wrote:Immediately followed by, "DRAT! What was it I did to fix this the last time?"#8 Is that happening AGAIN???
I was thinking more along the lines of "I fixed this! What the heck did you guys change?!"
In my case that would be: I am sure I fixed it - is my memory really that bad?
Jim trying new iPad Touch
9. "Oh crap, look at all this other questionable code near there..."
10. Why the hell did I use a PIC!?
JIm
If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman
Please Read: Code-of-Conduct
Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user
Level: Moderator
Joined: Wed. Mar 28, 2001
Posts: 28164 View posts
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
Isn't "blaming the innocents" a step too?
You also have to blame the guy who worked on it last and has left the company.
It wasn't me. Before my time...
3.1 - I must have found a compiler bug!
3.2 - Nope, obviously this is a silicon errata!
5.1 - F**K me blind, I should have waited to posted that compiler bug report!
|
"Experience is what enables you to recognise a mistake the second time you make it." "Good judgement comes from experience. Experience comes from bad judgement." "Wisdom is always wont to arrive late, and to be a little approximate on first possession." "When you hear hoofbeats, think horses, not unicorns." "Fast. Cheap. Good. Pick two." "Read a lot. Write a lot." "We see a lot of arses on handlebars around here." - [J Ekdahl] |
 |
Level: 10k+ Postman
Joined: Fri. Jul 1, 2005
Posts: 15419 View posts
Location: Basingstoke, Hampshire, UK
If you are debugging software, the first stage is to blame it on the hardware guys. If that doesn't work call it a compiler bug. If it is hardware you are debugging, the first stage is to blame it on the software guys.
Level: Moderator
Joined: Wed. Mar 28, 2001
Posts: 28164 View posts
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
I have given myself several black eyes as I do both.....
Yeah, I do too these days.
Anytime I write a code for a new project (besides designing its board) I prepare myself in advance that I will need to fix many silly bugs (hardware and/or firmware) during the tests. The number of bugs likely varies from 50 (if I am lucky ) up to 500 (if I am not 
).
My problem is that I can't sleep well till I finish properly every project I start.
Level: 10k+ Postman
Joined: Fri. Jul 1, 2005
Posts: 15419 View posts
Location: Basingstoke, Hampshire, UK
A very good point: it is important to consider, as part of the design, how you will debug your project - something so often missing in problems posted here!
Last step of new board circuit design: Where's the best points to place test point loops (especially on boards that have analog parts).