[Crash-utility] crash does not work with last fedora kernels?

[David Wysochanski]

I cannot share the vmcore unfortunately due to data contents.

There's something strange going on in my setup though.
I run the Python expect module ("pexpect" ) for automation and run
crash commands under that.
For some reason, when I run this gdb10 test branch, I get these weird errors.
But then I'm not seeing errors when I run the same commands manually
on the same vmcore and gdb10 test branch.
So it's the combination of the new gdb10 branch plus pexpect
environment where I see them, and only with some vmcores.
It's possible some crash output format changes and confuses pexpect,
and it's not a crash bug at all.
I've also seen some strange crash behavior when certain sequences of
crash commands are run.
I'll see if I can narrow down the problem further and report back.


On Fri, Jul 30, 2021 at 2:12 PM Alexey Makhalov <amakhalov at vmware.com> wrote:
>
> Hi David,
> Can you share vmcore and kernel images? Or provide an intructions how to recreate this core?
> I would be nice if you perform set of testing with your cores!
> Thanks,
> --Alexey
>
> On 7/30/21, 7:44 AM, "crash-utility-bounces at redhat.com on behalf of David Wysochanski" <crash-utility-bounces at redhat.com on behalf of dwysocha at redhat.com> wrote:
>
>     On Thu, Jul 29, 2021 at 9:57 PM lijiang <lijiang at redhat.com> wrote:
>     >
>     > >
>     > > 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsrc.fedoraproject.org%2Frpms%2Fkernel%2Fpull-request%2F48&data=04%7C01%7Camakhalov%40vmware.com%7Ceadd7163e75c4cd9858808d95368790e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637632530448673576%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Mwn4GKA5QMYpCcRpeKq26xhEJuOHDglXoHZk2uFa5DE%3D&reserved=0
>     > >
>     > > 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.
>     >
>
>     Yes, thank you.  But did you see my feedback about some of the error
>     output, when I tested your branch?
>     Do you have a list of existing issues?
>     I can fairly easily test your experimental branch on a series of
>     vmcores, if that helps.
>
>     Here's the feedback, cut/pasted from the other email thread:
>
>     I'm seeing a lot of "invalid input" displayed like the below when
>     using the '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"
>
>     --
>     Crash-utility mailing list
>     Crash-utility at redhat.com
>     https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flistman.redhat.com%2Fmailman%2Flistinfo%2Fcrash-utility&data=04%7C01%7Camakhalov%40vmware.com%7Ceadd7163e75c4cd9858808d95368790e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637632530448683569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HzS0X6Dz%2FDoTa121tQhGXGFih1T7s4YFMt7kghQA1ds%3D&reserved=0
>
>
>
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://listman.redhat.com/mailman/listinfo/crash-utility