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

Truncated core file when COMP_COMPRESSION is set to "true" #165

Open
amikugup opened this issue Oct 16, 2024 · 1 comment
Open

Truncated core file when COMP_COMPRESSION is set to "true" #165

amikugup opened this issue Oct 16, 2024 · 1 comment

Comments

@amikugup
Copy link

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
Copy link

Hi.

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

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