diff options
author | Tor Lillqvist <tlillqvist@novell.com> | 2011-05-23 00:16:46 +0300 |
---|---|---|
committer | Tor Lillqvist <tlillqvist@novell.com> | 2011-05-23 00:17:22 +0300 |
commit | 66f5c1fce04c39bc2eec86889f5109c62e4a33c1 (patch) | |
tree | 60c6d9cd910664c2d62231f2064b75e4018a969b /tools | |
parent | Drop OS2 (diff) | |
download | core-66f5c1fce04c39bc2eec86889f5109c62e4a33c1.tar.gz core-66f5c1fce04c39bc2eec86889f5109c62e4a33c1.zip |
Fix crash introduced in commit 2cc2e5b9a45887a53f01ad2fd324b6ed43f018ef
Really, for a command-line tool that can be run with minimal fuss, is it
really too much to expect changes to be tested?
Diffstat (limited to 'tools')
-rw-r--r-- | tools/bootstrp/addexes2/mkfilt.cxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/bootstrp/addexes2/mkfilt.cxx b/tools/bootstrp/addexes2/mkfilt.cxx index 98a0790d423f..ff958ba8e717 100644 --- a/tools/bootstrp/addexes2/mkfilt.cxx +++ b/tools/bootstrp/addexes2/mkfilt.cxx @@ -125,7 +125,7 @@ MkFilter::MkFilter( ByteString aInFile, ByteString aOutFile ) : MkFilter::~MkFilter() { - for ( size_t i = 0, n = pLst->size(); i < n; ++i ) { + for ( size_t i = 0, n = pTnrLst->size(); i < n; ++i ) { delete (*pTnrLst)[ i ]; } delete pTnrLst; |