Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in RAR5 solid files #7

Open
DrMcCoy opened this issue Jul 12, 2020 · 1 comment
Open

Bug in RAR5 solid files #7

DrMcCoy opened this issue Jul 12, 2020 · 1 comment
Assignees
Labels

Comments

@DrMcCoy
Copy link
Owner

DrMcCoy commented Jul 12, 2020

While testing for #4, I noticed a bug in our handling of RAR5 solid files. Sometimes, we produce broken output.

Example:
1.txt
blah
2.txt
foo

rar -ma5 -s a test.rar 1.txt 2.txt

This creates a solid RAR5 file we can't correctly decompress. The first file extracts fine, the second doesn't. Seems to be connected to our "finishing off" of the remaining of the solid block. I assume it produces output that belongs into the second file instead of just influencing the state?

@DrMcCoy DrMcCoy added the bug label Jul 12, 2020
@DrMcCoy DrMcCoy self-assigned this Jul 12, 2020
@DrMcCoy
Copy link
Owner Author

DrMcCoy commented Aug 20, 2020

As an update of sorts, I haven't yet found an easy way to fix this. It looks like I'll need to take apart solid file support and redo it mostly from scratch. I was basing it on partially wrong assumptions.

As a consequence, solid files are partially broken at the moment still. Partially meaning, it might work depending on the files that are bundled together in a solid chunk. Tiny files in particular are more prone to breaking. dmc_unrar isn't silently producing broken files, however, at least not as long as checksum validation is enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant