I also get the same problem when using ldapsearch 2.2.17 (the ldapsearch built from the version mentioned in the original report).