To use this debug version of Deadwood, enable the "SHOWPACKET" compile-time tag (such as with export FLAGS='-Os -DSHOWPACKET' before compiling Deadwood).
For Windows users, I have made a debug build of Deadwood with this flag set. It has the name "Deadwood-showpacket-20120922.exe"; use this binary to replace "Deadwood.exe" in Deadwood-3-2-02-win32.zip.
If this bug does not pop up again, I plan on releasing Deadwood 3.2.03 next month.
In addition, I have updated the documentation to reflect the fact that Windows 7 and any RHEL6 clone are now the supported OSes for Deadwood, added a note on Deadwood's use of malloc() (may not work with some embedded systems), as well as having Deadwood give out a more useful error message if chdir() fails (it now lets the user know which directory it tried to go to).
Downloads are here:
It can be downloaded here:
However, since it has been over a decade, I have created a new MaraDNS signing key which is signed with the old MaraDNS signing key (the paranoid amoung you can now breathe a sigh of relief). Barring a compromise of MaraDNS' private key, this will be the last MaraDNS GPG key I will generate until 2017, around the same time I update the OS MaraDNS is supported on.
I plan to work on MaraDNS/Deadwood again one day next month, after the 20th, unless a critical security bug with a CVE number is found.
To wit: If someone goes wrong with an Ultrabook and I'm in an exotic country, I am screwed until I can get back home to get the computer repaired. With my Sandy Bridge Inspiron 14z, on the other hand, when something goes wrong in an exotic country, I can go down to the local technology bazaar, pick up a standard part (a hard disk, in my case), and be working again within 24 hours.
It's just not worth paying $1,000 more for a computer that can not be repaired in the field -- nor have its memory upgraded -- just to have something that weighs one pound (1/2 a kilogram) less. 
In order to reduce spam, comments for this entry are now closed