Re: ordered indexing for integers

Hallvard B Furuseth wrote: > Howard Chu writes: >> Hallvard B Furuseth wrote: >>> Got crashes due to a write after 'tmp', incremented size by 1. >>> Haven't looked at why yet, or whether that's the complete fix. >> That should never happen. Do you have the backtrace from when the >> write occurred? > No, got memory corruption later. Valgrind pointed out the tmp write, > but I don't see in the doc how to get valgrind to core at first error. > If you run it with --db-attach it should prompt you for whether you want to drop into gdb on every error. Running your utils.c code (without the len+1 change) doesn't show any problems in ElectricFence. Strange.