[minicoredumper] Invalid stack when all memory regions are dumped

[John Ogness]

Hi Abi

On 2021-07-22, Abhi Arjun <abhiarjun at tutanota.com> wrote:
> Where you able to investigate and figure out the issue?

I can see where the problem is occurring, but I do not yet understand
why it is a problem. It will take some time to get this one.

> If it takes time, can I go back to old version of minicoredumper where
> stack is interpreted properly by gdb.

I expect all versions of the minicoredumper will have this problem. The
workaround is not to use "*" when setting "dump_by_name". It should be
enough for you to specify the pseudo-path and anonymous mappings. (You
do not need to specify the stack because minicoredumper has dedicated
settings for that.)

    "maps": {
        "dump_by_name": [
            "[vdso]",
            "[heap]",
            "[vvar]",
            "",
        ]
    }

Please test if this is enough for your needs.

The problem is occurring due to the file mappings, which are matched
when you use "*" here. I will continue investigating this issue.

> I couldn't find older versions of minicoredumper in the home page.

Here are the links to older versions. But I do not think you will find
that helpful. And I expect that they suffer from the exact same problem:

https://linutronix.de/minicoredumper/files/minicoredumper-2.0.0.tar.xz
https://linutronix.de/minicoredumper/files/minicoredumper-1.0.2.tar.gz
https://linutronix.de/minicoredumper/files/minicoredumper-1.0.1.tar.gz
https://linutronix.de/minicoredumper/files/minicoredumper-1.0.0.tar.gz

John Ogness