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

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(a)vmware.com&gt; 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, &quot;crash-utility-bounces(a)redhat.com on behalf of David Wysochanski" <crash-utility-bounces(a)redhat.com on behalf of dwysocha(a)redhat.com&gt; wrote: > > On Thu, Jul 29, 2021 at 9:57 PM lijiang <lijiang(a)redhat.com&gt; 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.fed... > > > > > > 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(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 -- Crash-utility mailing list Crash-utility(a)redhat.com https://listman.redhat.com/mailman/listinfo/crash-utility