ACM Home Page
Please provide us with feedback. Feedback
Kode Vicious Bugs Out
Full text HtmlHtml (10 KB),  PdfPdf (92 KB)
Source
Queue archive
Volume 4 ,  Issue 3  (April 2006) table of contents
Purpose-built Systems
DEPARTMENT: Kode vicious table of contents
Pages: 10 - 12  
Year of Publication: 2006
ISSN:1542-7730
Author
George Neville-Neil  ACM Queue
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 259,   Downloads (12 Months): 259,   Citation Count: 0
Additional Information:

abstract   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1127854.1127862
What is a DOI?

ABSTRACT

Dear KV, I'm on a small team that is building a custom, embedded, consumer device that is due out by Christmas. Of course the schedule is tight and there are make-or-break dates that if we miss basically mean the product will never make it to market. Not the most fun environment in which to have problems. The software was carefully specified and laid out and then simulated while the hardware was being manufactured. Now we have real hardware, and real problems as well. Aside from the timing issues we found when we were no longer running the software in a simulator, several bugs remain that show up only under very special circumstances and that disappear when I use the debugger or turn on the logging code built into the system. When tools fail you like this, what do you do next?


Collaborative Colleagues:
George Neville-Neil: colleagues