Setup.exe 2.510.2.2 segfaults when reinstalling a package with a changed md5sum
Version 2.510.2.2 of setup.exe segfaults when attempting to reinstall
the same version of a package that has a modified yet valid checksum.
This happens on Windows 2000 SP4, Windows 98 SE, and Windows XP SP2.
To reproduce the problem:
1) Generate and install a package as usual.
2) Keep the cached copy of the package around after you finish.
3) Regenerate the package such that its md5sum is different but its
version number is not. Adding a zero byte file to the package will work
nicely. Everything about the regenerated package should be valid in the
4) Ensure that the regenerated package installs successfully on a second
machine just to avoid any questions about the repackaging.
5) Attempt to reinstall the same version of the package on the first
machine using the same package cache area and the same mirror.
Setup.exe will segfault upon clicking the Next button on the package
selection page. Deleting the cached copy prior to running setup avoids
The correct behavior is obvously to avoid the segfault at all costs.
What to do with a package discovered in this state should be left up to
the user: Download a new copy and reinstall or just reinstall from the
I'll test out an updated version of setup.exe to verify any potential
fix if a download location is provided.