On Mon, Mar 3, 2008 at 4:53 PM, John Goerzen <jgoerzen@...>
> One of our Debian porters has noted that ./testo takes a vast amount of
> on some architectures. Enough that it crashes. Do you all have any
testo itself certainly has any such legitimate use for that kind of memory.
What you're seeing is an actual bug somewhere that testo is triggering.
(That's a good thing, actually...)
Do a "sh -x testo" until you find the failing command. Plop it into a
debugger for study. If it's one of the chained tests (read a, write b
then another gpsbabel reads b and compares against a) you might find it
happy to comment out the rm in the trap at the top of the script so that the
temp files are left in place.
ulimit -v can be handy for catching cases like this before they pile-drive
the system into the ground.