Comment # 20 on bug 1190434 from David Mair

I have a home project version of crash that appears to decode dwarf 5 debug
file format. However, I don't believe it is enough to resolve the problem using
coredumps on Tumbleweed.

Using kernel 6.0.10-1-default when I trigger a coredump creation then during
the creation of the coredump the following is displayed twice after beginning
to start the kdump kernel:

> The kernel version is unsupported
> The makedumpfile operation may be incomplete

Then, when I attempt to use the created coredump file the apparent memory for
the symbol linux_banner appears not to be present in the coredump. The result
being that crash will not start because it can't verify the kernel binary and
dumped kernel are the same version.

As a matter of care I repeated the test multiple times, using all the kernel
dump format options that create a file. In every case crash reports the
coredump has missing memory and fails to start.

Given that the creating of the coredump reported that the kernel version is
"unsupported" and that the makedumpfile may be "incomplete" and that crash
appears to find that there is missing memory in the coredump. I think we need
to consider why the attempt to create the coredump behaves the way it does
before further attempts to resolve crash.