Thank you very much for this bug report. I've checked in fixes for the bugs to CVS.
On Fri, Oct 10, 2003 at 11:51:24PM -0700, Michael Hunley wrote: > Hi Wei. > > I have just been running Valgrind on linux to track down memory errors in > my app. What an awesome tool. Certainly the best memory leek & corruption > tool I've ever seen. I wish it had a win32 distro. (For those curious, > look for version 1.9.6 since older versions are easier to find. Sorry, > don't have a good link handy since the kde developer site, which is the > normal host, seems to be having trouble; but another download site was around.) > > Anyway, it coughed up a complaint in my crypto++ (5.1 release). I found > some definite bugs and think I fixed the main one, but want to be sure. I > tried to get a diff with cvs, but I could not log in for some reason. So > here are the two files. Search for mgh in the comments and you will see > all the places I found potential issues. The fix to the main bug is in the > constructor for ByteQueue. There are two other potential bugs that I was > really unsure of in swap and in SetNodeSize; again mgh comments by all > issues I found. > > I hope this is helpful. Sorry I couldn't just send you a diff output. > > > Michael Hunley > Senior Engineer > PocketPurchase, Inc.
