Re: [Crash-utility] crash does not work with last fedora kernels?
On Wed, Jul 28, 2021 at 4:25 PM Alexey Makhalov <amakhalov(a)vmware.com> wrote:
Please try this and give us a feedback:
https://github.com/lian-bo/crash-gdb10.2-devel-temp
I'm seeing a lot of "invalid input" displayed like the below when
using 'bt' command. Is this a known issue?
bt: invalid input: "jne"
bt: invalid input: "mov"
bt: invalid input: "movl"
bt: invalid input: "jne"
bt: invalid input: "jne"
bt: invalid input: "jne"
bt: invalid input: "rep"
bt: invalid input: "je"
bt: invalid input: "je"
bt: invalid input: "je"
bt: invalid input: "call"
bt: invalid input: "call"
bt: invalid input: "jne"
bt: invalid input: "call"
bt: invalid input: "call"
bt: invalid input: "movl"
bt: invalid input: "mov"
bt: invalid input: "jne"
bt: invalid input: "mov"
bt: invalid input: "je"
bt: invalid input: "call"
On 7/28/21, 1:23 PM, "Alexey Makhalov"
<amakhalov(a)vmware.com> wrote:
DWARF-5 support was added in GDB-8.0. There GDB update to version 10.2 is going
on right now. It will solve the issue of kernels built with dwarf-5 debuginfo.
Thanks,
--Alexey
On 7/28/21, 11:14 AM, "crash-utility-bounces(a)redhat.com on behalf of David
Wysochanski" <crash-utility-bounces(a)redhat.com on behalf of
dwysocha(a)redhat.com> wrote:
On Wed, Apr 28, 2021 at 8:54 AM lijiang <lijiang(a)redhat.com> wrote:
>
> 在 2021年04月26日 19:17, crash-utility-request(a)redhat.com 写道:
> > Message: 3
> > Date: Mon, 26 Apr 2021 11:27:40 +0300
> > From: Vasily Averin <vvs(a)virtuozzo.com>
> > To: crash-utility(a)redhat.com
> > Subject: [Crash-utility] crash does not work with last fedora kernels?
> > Message-ID: <8f8782a9-3da6-5d3c-c509-8b8ec8a30957(a)virtuozzo.com>
> > Content-Type: text/plain; charset=utf-8
> >
> > It looks like Fedora kernels uses gcc11 and generates debuginfo in
DWARF 5 format.
> >
> > [root@localhost ~]# rpm -q crash
> > crash-7.2.9-5.fc35.x86_64
> > [root@localhost ~]# uname -a
> > Linux localhost.localdomain 5.11.12-300.fc34.x86_64 #1 SMP Wed Apr 7
16:31:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
> >
> >
> > [root@localhost ~]# crash -1
> > Dwarf Error: wrong version in compilation unit header (is 5, should be
2, 3, or 4) [in module /usr/lib/debug/usr/lib/modules/5.11.12-300.fc34.x86_64/vmlinux]
> > crash: gdb_session_init: pulling in debug data by accessing
init_mm.mmap
> > Dwarf Error: wrong version in compilation unit header (is 5, should be
2, 3, or 4) [in module /usr/lib/debug/usr/lib/modules/5.11.12-300.fc34.x86_64/vmlinux]
> >
> > crash: /usr/lib/debug/lib/modules/5.11.12-300.fc34.x86_64/vmlinux: no
debugging data available
> >
> > [root@localhost ~]# ls -al
/usr/lib/debug/lib/modules/5.11.12-300.fc34.x86_64/vmlinux
> > -rwxr-xr-x. 1 root root 679679112 Apr 7 20:14
/usr/lib/debug/lib/modules/5.11.12-300.fc34.x86_64/vmlinux
> > [root@localhost ~]# rpm -qf
/usr/lib/debug/lib/modules/5.11.12-300.fc34.x86_64/vmlinux
> > kernel-debuginfo-5.11.12-300.fc34.x86_64
> >
> > NB: last fc35 does not work too.
> >
>
> Thank you for reporting this issue, Vasily.
>
> The DWARF-5 caused this failure. I will have a look and try to handle this
issue later.
>
> Thanks.
> Lianbo
>
What's the status of this issue? Is this due to needing updated
embedded gdb or something else?
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flistman...
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://listman.redhat.com/mailman/listinfo/crash-utility