[minicoredumper] Debugging corrupt tar files (invalid sparse archive member)

[Jos Hulzink (Ellips B.V.)]

Hello,

We are facing an issue with the mini core dumps of our application: The tar files are quite often invalid (tar: core: invalid sparse archive member) and cannot be opened by any tool. We do get some valid dumps from the same application sometimes, so the tool is not completely broken.

We are trying to find out why this is happening, but we are looking for directions how to debug this. Any ideas ?

MiniCoreDumper 2.0.2, configuration can be found below.

Kind regards,

Jos Hulzink


{
    "stacks": {
        "dump_stacks": true,
        "first_thread_only": true,
        "max_stack_size": 0
    },
    "maps": {
        "dump_by_name": [
            "[vdso]"
        ]
    },
    "compression": {
        "compressor": "gzip",
        "extension": "gz",
        "in_tar": true
    },
    "dump_auxv_so_list": true,
    "dump_pthread_list": true,
    "dump_robust_mutex_list": true,
    "dump_scope": 1024,
    "live_dumper": false,
    "write_proc_info": false,
    "write_debug_log": false,
    "dump_fat_core": false
}
~
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linutronix.de/pipermail/minicoredumper/attachments/20230206/f2f9bc32/attachment.htm>