p4-dpdk-target
p4-dpdk-target copied to clipboard
Shell input issues
@lzhzero and I have identified several shell input issues, that might relate to each other. So we decided to use this single issue to report them all at once.
Issue 1: shell corruption after bf_switchd
exit
After exiting from a bf_switchd
process back to a shell, when you type, there will be nothing shown. After typing ENTER, you shall see the characters typed were recorded. They were just not displayed.
A quick fix to this issue is to type reset
followed by ENTER. This will reset shell states to bring it back to normal. But it would be nice not having to do this every time.
Issue 2: bfshell
exit leads to bf_switchd
segfault
In terminal 1, run bf_switchd
. In terminal 2, run bfshell
to execute some commands. Now quit bfshell
in terminal 2, and you shall see bf_switchd
getting a segfault error in terminal 1.
We are not sure if this is the expected behavior though.
Issue 3: messed up input in VS Code integrated terminal
In a VS Code integrated terminal, start bf_switchd
, and follow by bfshell> tdi_python
. Now start typing, and you shall notice random characters popping up.
This might be an issue on the VS Code side though. We are not sure.
Acknowledged, will try to take a look