Hi Charles
This bug has been detected and corrected.
The latest source code in the "dev" branch,
available at :
corrects it.
The test suite has also been upgraded to detect such case from now on.
Temporary work around is to use --no-sparse command line option.
The work around will also remain fully compatible with future versions r130+.
Regards