-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sane keyboard input not working in GDB when using the fbt tool #1787
Comments
@drunkbatya we might need your help with that one. |
OK, in case it helps, it appears to be basically an issue with ncurses. If I remove the ncurses library from the path that the scripts append, it works fine with the system ncurses. |
@Semptum we've pushed couple updates, is your issue still there? |
Yup, just checked, the problem persists on the latest dev even though it pulled in newer versions of the tools |
Yup, just checked, the problem persists on the latest dev even though it pulled in newer versions of the tools. |
@hedger @drunkbatya your turn ;) |
@Semptum we've pushed couple toolchain updates, do you still have this issue? |
Yup, still there... |
Ok, I'll look at this soon |
@drunkbatya any updates? |
Not yet, I'll look at this today. |
@Semptum
|
Describe the bug.
When using
./fbt blackmagic
, agdb
interface appears. However, pressing backspace graphically adds a space to the prompt (as long as there is text to erase). Functionnally the text is erased but not graphically.Similar behavior arises as soon as the text is changed in any way such as pressing the left arrow and typing something as illustrated below.
Reproduction
cd
to the directory of the firmwaregdb
./fbt blackmagic
Target
No response
Logs
No response
Anything else?
The system is Arch Linux with KDE. The Terminal emulator is Konsole but the problem persists in the virtual console and in XTerm. The shell is ZSH but the problem persists in SH and BASH.
I was advised to add "TERM" to the environment variables at line 15 of
environ.scons
but this did not help.EDIT: The problem comes from the binary
arm-none-eabi-gdb
in thetoolchain
folder. The system version works fine. The shipped version has this problem.The text was updated successfully, but these errors were encountered: