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

ERROR: unknown (de)compression error 4294967287 in rep:1kb #3

Open
john-peterson opened this issue Aug 24, 2023 · 5 comments
Open

ERROR: unknown (de)compression error 4294967287 in rep:1kb #3

john-peterson opened this issue Aug 24, 2023 · 5 comments

Comments

@john-peterson
Copy link
Contributor

john-peterson commented Aug 24, 2023

cabal run freearc -- create a compile
Up to date                                    FreeArc 0.67 (March 15 2014) creating archive: a.arc                                                                                      Compressed 1 file, 87 => 99 bytes. Ratio 113.79%                                            Compression time: cpu 0.00 sec/real 0.01 sec  All OK

cabal run freearc -- t a.arc
Up to date
FreeArc 0.67 (March 15 2014) testing archive: a.arc                                         Testing 1 file, 87 bytes. Processed   0%
ERROR: unknown (de)compression error 4294967287 in rep:1kb

I collected more output from another build

https://github.com/john-peterson/freearc

../john-peterson/Unarc/unarc t a.arc
footer: "ArC" in the last 0x1000 bytes        block: ArC 4 lzma:1mb:normal:bt4:32 53 63 f0ef15ff                                          size: 0x35==0x35                              crc: 0xf0ef15ff==0xf0ef15ff                   descriptor: 0000000000 +0x008
descriptor: 0x0000000082 +0x051               comment: 0 0                                  . Testing archive: a.arc                      size: 0x48==0x48                              crc: 0x12d574f4==0x12d574f4
data: 0x000000001f +0x00063 rep:1kb+exe+delta+lzma:32kb:normal:16:mc8                       1 files
Testing compile (87 bytes)                    ERROR: file compile failed CRC check          
@john-peterson
Copy link
Contributor Author

john-peterson commented Aug 24, 2023

the file structure is correct but the data block is corrupted

I will add more debugging output to that portion of the test

@john-peterson
Copy link
Contributor Author

Can you reproduce it in Mac?

@john-peterson
Copy link
Contributor Author

I tried to test other compression schemes by using other files but it failed

cabal run freearc -- create a README.md
Up to date                                    FreeArc 0.67 (March 15 2014) creating archive: a.arc                                        Compressing 1 file, 959 bytes. Processed   0%Segmentation fault

@john-peterson
Copy link
Contributor Author

john-peterson commented Aug 24, 2023

I also found a bug in my build with plain text files

This is surprising since I did not change anything

Did he fix it before he created the build?

Is it specific to the build targets? My unarc.exe use the exact same headers right?

This is the beta release build

wine ../arc/arc.exe create a README.md
FreeArc 0.67 (March 15 2014) creating archive: a.arc                                                                                      Compressed 1 file, 959 => 503 bytes. Ratio 52.45%                                           Compression time: cpu 0.00 sec/real 0.07 sec = 0%. Speed 0.01 mB/s                          All OK

wine ../arc/unarc.exe t a.arc
FreeArc 0.67 unpacker. Testing archive: a.arc
Testing README.md (959 bytes)                 All OK

This is the beta release source

../john-peterson/Unarc/unarc t a.arc
data: 0x000000001f +0x001f7 dict:2kb:80%:l8192:m400:s100+lzp:2kb:90%:65:h11:d1mb:s16+ppmd:8:96mb                                          1 files                                       Testing README.md (959 bytes)                 Segmentation fault

wine ../john-peterson/Unarc/unarc.exe t a.arc
Testing archive: a.arc                      size: 0x64==0x64                              crc: 0x6686fb6a==0x6686fb6a
wine: Unhandled page fault on read access to 000001F0 at address F7C635D2 (thread 0009), starting debugger...

@despawnerer
Copy link
Owner

Huh, curious. It definitely did work earlier, so something must've gotten screwed up at some other point.

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

No branches or pull requests

2 participants