Unsolved CentOS 7 debugger dont show debug info
-
Hello. Centos 7. gcc 7.3., gdb 8.0.1-36.el7, cmake3 3.11.2, python 2.7.5 (I use devtoolset-7)
Qt installed separately from qt-opensource-linux-x64-5.11.0.run.Debugger stops, continues, etc, but does not showing debug info, stack call, current line, etc. How to fix this?
-
It seems, that all theses things exists, but does not showing, because if I click on empty areas, with of columns changing, i can right click and have context menu. Thus, it only not drawing this text, lines, but they presents. How to show them?
-
@Sacha_D What happens if you stop at line 57?
-
@jsulm The same thing. It stops, It go by F10 from 56 to 57. It shows value of a and other variables in popup-window, when I hover mouse pointer on variable. I installed Qt Creator 4.6.2 instead of 4.6.1. The same thing. I tried to change fonts...
-
@Sacha_D If you start QtCreator from a terminal do you see any warnings/errors in the terminal?
-
End of debugger log:
&"python theDumper.fetchStack({"limit":20,"nativemixed":0,"token":21})\n"
&"Traceback (most recent call last):\n"
&" File "<string>", line 1, in <module>\n"
&" File "/opt/Qt5.11.0/Tools/QtCreator/share/qtcreator/debugger/gdbbridge.py", line 1304, in fetchStack\n"
&" objfile = fromNativePath(symtab.objfile.filename)\n"
&"UnicodeEncodeError: 'ascii' codec can't encode characters in position 34-39: ordinal not in range(128)\n"
&"Error while executing Python code.\n"
21^error,msg="Error while executing Python code." -
@jsulm in terminal I see only "Emty filename passed to function"
-
@Sacha_D said in CentOS 7 debugger dont show debug info:
"UnicodeEncodeError: 'ascii' codec can't encode characters in position 34-39: ordinal not in range(128)\n"
Could be an encoding problem.
-
@jsulm The problem was that the path to project contained russian-named folder.
-
@Sacha_D For developing it is always safe to use paths with ASCII characters and without spaces.