Kazuhito Hagio

Maybe it does not support recent kernels. Could you consult the maintainer first? https://github.com/fujitsu/crash-trace

Hi muryliang, What is the version of makedumpfile that you're using to capture the vmcore? I saw a similar message on Linux 6.2 once [1], upstream makedumpfile-1.7.3 and later support...

> For Ubuntu makedumpfile, please consult Ubuntu community. Probably this is it: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248 Please try.

I can build the latest crash on Ubuntu 20.04.6. Probably lack of packages. Please try: ``` # apt install git gcc g++ make wget tar patch bison texinfo libncurses-dev zlib1g-dev...

hmm, no runqueues found? I've not seen it on 6.5. What does gdb print? ``` $ gdb vmlinux (gdb) whatis runqueues type = struct rq (gdb) info address runqueues Symbol...

Thanks, that looks sane... There may be something strange in `per_cpu_symbol_search()`, is it possible to check why it's not found? I think these should be like this normally... ``` #...

I could reproduce it, 6.1.12 has `.symtab` but 6.5.9 doesn't have `.symtab` after `eu-strip --strip-all`. It looks like crash can start session at least with `--keep-section=.symtab`. gdb-10.2 itself can read...

@bhupesh-sharma @lian-bo (Seems editing a comment doesn't send a notification..) It looks like RHEL8 also has the same or a similar issue. I could reproduce it on RHEL8.2 for arm64...

@lian-bo, thanks for the info. But I'm not sure whether the gdb behavior you showed is the same as this issue in crash. I tried the following and it looks...

I'll see if the patch can be applied to the crash utility later on. Rebasing gdb should be a very tough work for us (at least for me), so I...