Truncated core file when COMP_COMPRESSION is set to "true"

[amikugup]

We are observing a strange issue with IBM core dump handler. Actually, we are getting truncated core file when COMP_COMPRESSION flag is set to "true". gdb is complaining about the truncated file and core file size is close to 900 MB while gdb is expecting a core file size of 3 GB.

We didn't see any such issue when we turned off the compression. we got a full core file and gdb is also happy.
Is this a known issue with the compression flag?

[pereyra-m]

Hi.

I'm getting problems too with big dumps, they can't be read with gdb.
I'll try without compression.

[No9]

Let me know how you get on
We use the zip crate and just use 'COMP_COMPRESSION' as a flag so I'd say it's likely a bug in that crate.

core-dump-handler/core-dump-composer/src/main.rs

Line 118 in 327ed2e

zip::CompressionMethod::Deflated

Looks like a lot has been added to zip as it's now on version 2.2.0 so a PR with a bump would be appreciated.

Thanks

[pereyra-m]

Hi again.

We were using the 8.6.0 version, and even when the flag was set to "false", the dumps were uploaded compressed and the big ones were corrupt.
The release notes show that this was solved in recent versions, so we upgraded to 8.10.0 and now it's working.

[amikugup]

We are already using v8.10.0 but that doesn't solve the problem and we still need to disable the compression to make this work. @pereyra-m this would be helpful if you can share more details regarding the core file size that you have tried and configurable value you are using.

[pereyra-m]

We haven't any special configuration, and we noticed the corruptions when the dumps were higher than 1GB more or less.
The error was something like

Failed to read a valid object file image from memory.

Maybe in your case is something else.