On Sat, Jul 31, 2021 at 5:33 AM lijiang <lijiang@xxxxxxxxxx> wrote:
>
> > 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?
>
Sure thing Lianbo - I will revert the above, retest, and report back.
> 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"
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/crash-utility
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/crash-utility
