January/February 2018 issue of acmqueue

The January/February issue of acmqueue is out now

Kode Vicious


  Download PDF version of this article PDF

ITEM not available


Originally published in Queue vol. 12, no. 6
see this item in the ACM Digital Library


Follow Kode Vicious on Twitter
and Facebook

Have a question for Kode Vicious? E-mail him at [email protected]. If your question appears in his column, we'll send you a rare piece of authentic Queue memorabilia. We edit e-mails for style, length, and clarity.


Jez Humble - Continuous Delivery Sounds Great, but Will It Work Here?
It's not magic, it just requires continuous, daily improvement at all levels.

Nicole Forsgren, Mik Kersten - DevOps Metrics
Your biggest mistake might be collecting the wrong data.

Alvaro Videla - Metaphors We Compute By
Code is a story that explains how to solve a particular problem.

Ivar Jacobson, Ian Spence, Pan-Wei Ng - Is There a Single Method for the Internet of Things?
Essence can keep software development for the IoT from becoming unwieldy.


(newest first)

Edward Kimball | Fri, 04 Jul 2014 03:52:09 UTC

Binary search is a great idea, especially for a bug that vanishes with the debugger operating.

In addition to the possibility of a timing bug, it sounds to me like it might be a memory leak or buffer overflow problem. Without debugging, the leak may trample some useful code and cause the bug. The debugger may move things around so that the leak overwrites some less harmful memory location. In that case, adding print statements might also affect what areas the leak overwrites and cause the bug to vanish from the modified code.

Martin Leiser | Thu, 03 Jul 2014 21:12:15 UTC

I binary search can hardly be underestimated in its efficiency of reproducible bugs... Theory is your friend... I love it, if there is no faster plan.

Leave this field empty

Post a Comment:

© 2018 ACM, Inc. All Rights Reserved.