News for hackers. Stuff that matters.
Re:Sometimes the bug isn't in your code, it's in the CPU by mbateman on Monday March 05, 2012 @10:06PM (#3669461)
I also looked this up, and found the original paper that coined the term, which starts:

> The "Wolf Fence" method of debugging time-sharing programs in higher languages evolved from the "Lions in South Africa" method that I have taught since the vacuum-tube machine language days. It is a quickly converging iteration that serves to catch run-time errors.

http://dl.acm.org/citation.cfm?id=358695 (if you have access)

Anyone know what the "Lions in South Africa" method is? I couldn't find it via Google, it just kept turning up references to the same paper.

Re:Sometimes the bug isn't in your code, it's in the CPU by prolepunk on Tuesday March 06, 2012 @12:09AM (#3669729)
After a quick googling I found this explanation of wolf-fence debugging:

http://coreygoldberg.blogspot.com/2008/12/wolf-fence-debuggi...

It stipulates that the state of Alaska has got exactly one wolf, so you build a fence across the middle of the state to find on which side wolf would howl, then subdivide the problem, etc...

I'm assuming in your case the wolf got replace with a lion and Alaska with South Africa.

Re:Sometimes the bug isn't in your code, it's in the CPU by slavak on Tuesday March 06, 2012 @03:57AM (#3670216)
Personally I always preferred the mathematician's method for catching a lion in the Sahara...
Re:Sometimes the bug isn't in your code, it's in the CPU by gaius on Tuesday March 06, 2012 @05:06AM (#3670369)
First, place a lion in Egypt so you know your algorithm will terminate...
Re:Sometimes the bug isn't in your code, it's in the CPU by jaylevitt on Tuesday March 06, 2012 @09:06AM (#3671001)
Typical global-warming propaganda.. :)