Hi Lianbo,
On 25/11/24 15:26, lijiang wrote:
Hi, Aditya
Thank you for the fix.
On Wed, Oct 9, 2024 at 7:08 PM Aditya Gupta <adityag@xxxxxxxxxxxxx> wrote:
Few vmcores don't have vmcoreinfo elf note, such as those created
using
virsh-dump.
I tried to generate a core dump file with "virsh dump" and got an
error message:
# ./crash vmlinux ../coredump
crash 8.0.6
Copyright (C) 2002-2025 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, 2020-2024 NEC Corporation
Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
Copyright (C) 2015, 2021 VMware, 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.
WARNING: --vmcoreinfo is empty, will read from symbols
This warning is added in this patch, when vmcoreinfo is empty. Though
maybe I did some typo here, I don't like it showing '--vmcoreinfo'
instead of just 'vmcoreinfo', will check this also.
crash: gdb_interface: gdb not initialized?
Could you please double check?
BTW: the kernel version is 6.12, I tested it based on aarch64 machine.
Sorry I don't have a aarch64 system, will check it on ppc64le.
It showing "gdb not initialised" is weird, that should depend on
GDB_INIT flag, and this patch shouldn't touch it. Will check.
Thanks,
Aditya Gupta
--
Crash-utility mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxxxxxx
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines: https://github.com/crash-utility/crash/wiki
