Open tom-seewald opened 3 years ago
Do you need the System.map file? Please see mapfile
on the man page.
(It looks like crash-7.3.0-3.fc35 does not have 68870c83d299603c07785e3530e33c13045c87ef, so cannot be used for 5.16 in the first place.)
Do you need the System.map file? Please see
mapfile
on the man page.
Well I'm running 5.15.4 right now, as I didn't want to stay on a kernel that is unstable for me. If I use /boot/System.map-5.16.0-rc2
I also get the same behavior described above, if I do not specify a System.map file it tells me there's a kernel version mismatch.
if I do not specify a System.map file it tells me there's a kernel version mismatch.
yes, I meant the following command:
$ sudo ~/crash/crash linux/vmlinux /var/crash/127.0.0.1-2021-11-24-16\:45\:46/vmcore
if this tells a version mismatch, what do the following commands print?
# file vmlinux
# crash -d 1 vmlinux vmcore
if this tells a version mismatch, what do the following commands print?
# file vmlinux
That should be in my original message.
# crash -d 1 vmlinux vmcore
The output is over 400 lines, but it looks like there is a build id mismatch. However it is the same config, compiler, and kernel version.
if this tells a version mismatch, what do the following commands print?
# file vmlinux
That should be in my original message.
oh, sorry, I missed that.
# crash -d 1 vmlinux vmcore
The output is over 400 lines, but it looks like there is a build id mismatch. However it is the same config, compiler, and kernel version.
I'm not sure what does it, but no guarantee that symbol addresses are consistent. Please try the vmlinux having the same id as the vmcore.
System info: Architecture: x86_64 Crash versions: 8.0.0 and crash-7.3.0-3.fc35 Kernel version: 5.16.0-rc2 (locally built mainline) OS: Fedora 35
Scenario: I am attempting to debug a 5.16-rc2 vmcore file using crash. The kernel was built locally and I have enabled debug symbols. I have tried using the version of crash shipped with Fedora as well as the latest upstream version.
Problem: For both
crash 8.0.0
andcrash-7.3.0-3.fc35
the utility appears to start however it abruptly ends without any error being logged. Systemd'scoredumpctl
doesn't show any coredumps being generated by crash either.Example attempts to debug the vmcore file using crash: