For instance, consider the following command :
$ 7z d LargeArchive.7z some/file/in/archive.foo
If this is interrupted ( say, using CTRL + C, or if the update callback's SetCompleted method returns E_ABORT ), p7zip segfaults.
This only appears to occur with updates involving deletion. While I haven't had time to investigate this, it appears to be a thread synchronization issue. Depending on how soon you interrupt the process, one of the following events can occur :
1. Everything goes fine. This only happens if you abort immediately, before the actual update starts.
2. Freezes ( I suspect due to a wait condition somewhere )
My environment : p7zip Version 9.13 (locale=utf8,Utf16=on,HugeFiles=on,2 CPUs) / Mac OS X 10.6.6 /
Log in to post a comment.