[Crash Utility] Improvement for getting offline CPU register without symbol "crash_notes"
by James Hsu (徐慶薰)
Dear crash_tool maintainers,
We want to improve the crash_tool for the case that need offline cpu register info even Kdump without crash_notes.
For one thing, we will prepare a Kdump with all CPU register info in ELF note.
For another thing, we need to modify crash_tool and make it support adding offline cpu register info even Kdump without crash_notes.
We prepare a patch for the case with ARCH=arm64.
Please take your time to review our patch and look forward to receving your comments.
BR
James Hsu
3 years
Re: [Crash-utility] crash does not work with last fedora kernels?
by lijiang
>
> Hi, David
> Thank you for the attention.
> Currently, Fedora kernel has been forced to generate the DWARF4 debuginfo
via the
> CONFIG_DEBUG_INFO_DWARF4 kernel option, see jforbes' comment:
> https://src.fedoraproject.org/rpms/kernel/pull-request/48
>
> Once crash gdb is upgraded, the DWARF5 could be enabled again in Fedora
kernel.
>
> BTW: that is a temporary branch, still under tests and it has not been
announced yet.
>
> Lianbo,
> Please STOP replying to the digest, but reply properly on the
> appropriate email thread.
> I've been involved in a lot of open source projects over the past 15
years,
> and you're the only one I've ever seen that replies to a digest, not the
> appropriate email thread.
Good suggestions, David.
I remember that you reminded me about this issue before this time. But
recently my email system switched to Gmail, and made a mistake again. I'm
trying to get used to the Gmail
system.
But anyway, I hope that my last reply answered your questions.
Thanks.
Lianbo
3 years, 1 month
Re: [Crash-utility] crash does not work with last fedora kernels?
by lijiang
>
> The revert fixed the problem - thanks for the suggestion!
>
> I will understand if it turns out we cannot guarantee output format
> from release to release - I am not sure what the options are with the
> underlying issue(s).
>
This is a good question. We are trying our best to cover various cases. So
far we have noticed that some options could have potential issues in crash
utility, such as "max-completion/max-value-size/width/height"...
> If for some reason this cannot be fixed up, and output needs to change,
> maybe at least describe how output will change in the commit message.
>
Good idea.
It's not fully clear what happened in this automation - I didn't get a
> chance to track down what happened as it only occurred in certain
> vmcores and possibly with certain sequences of commands.
>
> Let me know if you want further testing.
>
>
Thank you, David. I have a lot of vmcores that Dave left. And I'm using
these old vmcores
to test crash utility. But, any feedback will be appreciated.
Thanks.
Lianbo
3 years, 1 month
Re: [Crash-utility] crash does not work with last fedora kernels?
by lijiang
> Here's the feedback, cut/pasted from the other email thread:
>
Thank you for the feedback.
> I'm seeing a lot of "invalid input" displayed like the below when
> using the 'bt' command. Is this a known issue?
>
Yes. This is a regression issue, which may be caused by the following
patch:
a3ea92bcae1f ("Fix for the tab completion output issues")
Would you mind reverting the above patch and trying it again?
Thanks.
Lianbo
> 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"
3 years, 1 month
