Comment 9 for bug 998584

I used last wartool version from bzr and warcraft data from Miguel. Wartool did not crached on both 32 and 64 bit Ubuntu 12.04 systems. Output from valgrind did not show any errors:

$ valgrind --leak-check=full --show-reachable=yes ./wartool ../war2/data unpack
==14180== Memcheck, a memory error detector
==14180== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==14180== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==14180== Command: ./wartool ../war2/data unpack
==14180==
Note: Data is already extracted in Dir "unpack" with this version of wartool
Detected UK/Australian original DOS CD
Extract from "../war2/data" to "unpack"
Please be patient, the data may take a couple of minutes to extract...
Archive "../war2/data/rezdat.war"
Archive "../war2/data/strdat.war"
Archive "../war2/data/maindat.war"
Archive "../war2/data/sfxdat.sud"
Archive "../war2/data/rezdat.war"
Archive "../war2/data/snddat.war"
Archive "../war2/data/muddat.cud"
Done.
==14180==
==14180== HEAP SUMMARY:
==14180== in use at exit: 0 bytes in 0 blocks
==14180== total heap usage: 15,157 allocs, 15,157 frees, 427,965,094 bytes allocated
==14180==
==14180== All heap blocks were freed -- no leaks are possible
==14180==
==14180== For counts of detected and suppressed errors, rerun with: -v
==14180== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)