GDB Remote Debugging - Cannot instantiate printer for default visualizer

China☆狼群 提交于 2020-06-13 06:14:12

问题


Setting up remote gdb debugging in eclipse . The debugger will step through the code just fine but, all of the variables show the following error:

1) Failed to execute MI command: -var-create - var_Name Error message from debugger back end: Cannot instantiate printer for default visualizer

Basically, values don't show up for the variables. Is there a setting for the .gdbinit file to fix this, or some other setting in eclipse?

  • The remote device uses NFS to mount the localhost /path/to/app
  • compiler: gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf
  • localhost: running linux mint 19.2 and using arm-linux-gnueabihf-gdb
  • remote: gdbserver :port /path/to/app

    user@localhost:/ gdb --version
    GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
    

回答1:


From Eclipse Main window: Window -> Preferences -> C/C++ -> Debug -> GDB : Under Pretty Printing region, Deselect "Enable pretty printers in variable/expression tree"

Then click "Apply" and "Apply and Close" viola the variables now print out during remote debug sessions. No change to my .gdbinit file was needed.

Perhaps I am not using python-enabled GDB... I am not sure.



来源:https://stackoverflow.com/questions/59886832/gdb-remote-debugging-cannot-instantiate-printer-for-default-visualizer

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!