crash CoreDump and namelist don't match though my release matches the namelist file
I'm trying to 'read' a .crash file in /var/crash.
I've download the correct namelist/vmlinux image for use with my system and crash following these instructions. I've also 'extracted' the CoreDump via apport-unpack. the original .crash file is "_usr_bin_krunner.1000.crash." I have the namelist in /usr/lib/debug/boot. The vmlinux debug image/file matches my release:
user@kubuntu18:/var/crash/krunner$ uname -r
4.15.0-43-generic
&
user@kubuntu18:/usr/lib/debug/boot$ l
vmlinux-4.15.0-43-generic
Now, when I go to analyze a .crash file's CoreDump in /var/crash, I get the following output:
user@kubuntu18:/var/crash/krunner$ sudo crash /usr/lib/debug/boot/vmlinux-4.15.0-43-generic CoreDump
crash 7.2.1
Copyright (C) 2002-2017 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
The key error being:
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
I also noticed crash outputs:
This GDB was configured as "x86_64-unknown-linux-gnu"...
There is a /usr/lib/debug/lib/x86_64-linux-gnu directory (instead of debug/boot) which has a bunch of .so files... so I'm not sure if I should be using that folder to try and read the CoreDump?
My question is... am I using the right namelist to read this CoreDump? Or am I off in trying to read this CoreDump?
kubuntu crash logging
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
add a comment |
I'm trying to 'read' a .crash file in /var/crash.
I've download the correct namelist/vmlinux image for use with my system and crash following these instructions. I've also 'extracted' the CoreDump via apport-unpack. the original .crash file is "_usr_bin_krunner.1000.crash." I have the namelist in /usr/lib/debug/boot. The vmlinux debug image/file matches my release:
user@kubuntu18:/var/crash/krunner$ uname -r
4.15.0-43-generic
&
user@kubuntu18:/usr/lib/debug/boot$ l
vmlinux-4.15.0-43-generic
Now, when I go to analyze a .crash file's CoreDump in /var/crash, I get the following output:
user@kubuntu18:/var/crash/krunner$ sudo crash /usr/lib/debug/boot/vmlinux-4.15.0-43-generic CoreDump
crash 7.2.1
Copyright (C) 2002-2017 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
The key error being:
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
I also noticed crash outputs:
This GDB was configured as "x86_64-unknown-linux-gnu"...
There is a /usr/lib/debug/lib/x86_64-linux-gnu directory (instead of debug/boot) which has a bunch of .so files... so I'm not sure if I should be using that folder to try and read the CoreDump?
My question is... am I using the right namelist to read this CoreDump? Or am I off in trying to read this CoreDump?
kubuntu crash logging
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
add a comment |
I'm trying to 'read' a .crash file in /var/crash.
I've download the correct namelist/vmlinux image for use with my system and crash following these instructions. I've also 'extracted' the CoreDump via apport-unpack. the original .crash file is "_usr_bin_krunner.1000.crash." I have the namelist in /usr/lib/debug/boot. The vmlinux debug image/file matches my release:
user@kubuntu18:/var/crash/krunner$ uname -r
4.15.0-43-generic
&
user@kubuntu18:/usr/lib/debug/boot$ l
vmlinux-4.15.0-43-generic
Now, when I go to analyze a .crash file's CoreDump in /var/crash, I get the following output:
user@kubuntu18:/var/crash/krunner$ sudo crash /usr/lib/debug/boot/vmlinux-4.15.0-43-generic CoreDump
crash 7.2.1
Copyright (C) 2002-2017 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
The key error being:
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
I also noticed crash outputs:
This GDB was configured as "x86_64-unknown-linux-gnu"...
There is a /usr/lib/debug/lib/x86_64-linux-gnu directory (instead of debug/boot) which has a bunch of .so files... so I'm not sure if I should be using that folder to try and read the CoreDump?
My question is... am I using the right namelist to read this CoreDump? Or am I off in trying to read this CoreDump?
kubuntu crash logging
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
I'm trying to 'read' a .crash file in /var/crash.
I've download the correct namelist/vmlinux image for use with my system and crash following these instructions. I've also 'extracted' the CoreDump via apport-unpack. the original .crash file is "_usr_bin_krunner.1000.crash." I have the namelist in /usr/lib/debug/boot. The vmlinux debug image/file matches my release:
user@kubuntu18:/var/crash/krunner$ uname -r
4.15.0-43-generic
&
user@kubuntu18:/usr/lib/debug/boot$ l
vmlinux-4.15.0-43-generic
Now, when I go to analyze a .crash file's CoreDump in /var/crash, I get the following output:
user@kubuntu18:/var/crash/krunner$ sudo crash /usr/lib/debug/boot/vmlinux-4.15.0-43-generic CoreDump
crash 7.2.1
Copyright (C) 2002-2017 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. Enter "help copying" to see the conditions.
This program has absolutely no warranty. Enter "help warranty" for details.
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
The key error being:
WARNING: cannot read linux_banner string
crash: /usr/lib/debug/boot/vmlinux-4 and CoreDump do not match!
I also noticed crash outputs:
This GDB was configured as "x86_64-unknown-linux-gnu"...
There is a /usr/lib/debug/lib/x86_64-linux-gnu directory (instead of debug/boot) which has a bunch of .so files... so I'm not sure if I should be using that folder to try and read the CoreDump?
My question is... am I using the right namelist to read this CoreDump? Or am I off in trying to read this CoreDump?
kubuntu crash logging
kubuntu crash logging
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
edited Jan 25 at 21:47
YMGenesis
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
asked Jan 25 at 21:21
YMGenesisYMGenesis
286
286
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112915%2fcrash-coredump-and-namelist-dont-match-though-my-release-matches-the-namelist-f%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112915%2fcrash-coredump-and-namelist-dont-match-though-my-release-matches-the-namelist-f%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
