Blog: #debugging

12 Nov 2023:

Debug helpers in coverage.py  also: #coverage #dev-mindset

20 Mar 2021:

Machete mode: tagging frames

13 Jan 2020:

Bug #915: solved!

27 Oct 2019:

Debugging TensorFlow coverage

22 Dec 2016:

Finding test coupling  also: #development #testing

14 Mar 2015:

Finding temp file creators  also: #python

10 Nov 2013:

Ad-hoc data breakpoints  also: #python

24 Aug 2011:

Stack ninjas  also: #hacks #python

2 Mar 2010:

Trace function debugging challenge  also: #help #python

22 Nov 2009:

Memory leak mystery  also: #coverage #testing

5 Jul 2009:

A nasty little bug  also: #coverage #development

24 Nov 2008:

Print this file, your printer will jam  also: #history #postscript #printing

27 Sep 2008:

A server memory leak  also: #django

19 Jul 2008:

FirePHP  also: #tools

7 Nov 2007:

Chris Lomont and the Excel formatting bug  also: #math

8 Apr 2007:

My .pdbrc  also: #python

3 Aug 2006:

Helpful un-helpful magic  also: #databases

3 Jun 2006:

50-year-old bug

5 Mar 2006:

Everything in the same minute  also: #coding

1 Dec 2005:

Windows notification icons  also: #ui #windows

30 Nov 2005:

Reap what you sow

6 Oct 2005:

HTTP error 191

2 Sep 2005:

Interactive debugging in Python  also: #python

26 May 2005:

Of course, sometimes it is your software’s fault  also: #concurrency #databases

3 Mar 2005:

C# and OutputDebugString  also: #c#

15 Dec 2004:

The pitfalls of fixing error handling first  also: #development

2 Dec 2004:

C++ constructor trivia  also: #c++ #exceptions

4 Jun 2004:

Omniscient debugging  also: #java

9 Jan 2004:

Memory errors

8 Oct 2003:

Kernighan on debugging clever code  also: #quotes

2 Oct 2003:

A client crash hunted down

27 Sep 2003:

A server crash hunted down

18 Jul 2002:

Flaky coffee grinder