如何解决Qt Creators变量“<不可访问>”。行为? [英] How to solve Qt Creators variable-"<not accessible>" behavior?

查看:169
本文介绍了如何解决Qt Creators变量“<不可访问>”。行为?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我遇到的问题与变量中描述的相同在QT Creator中无法访问的本地和表达式中,但我想找到一种方法来修复 Qt Creator,以再次在调试窗口中显示默认的复合类型,例如std :: string。



我已经通过dist升级(fedora 18 => 20)从Creator 2.8更新到3.0,并且我知道那里可能出问题了,但是我真的想避免只为Qt重新安装整个操作系统造物主。



有什么方法可以使造物主更加冗长或将其写入日志文件?



是否已知Qt Creator 3.0会为复合类型显示漂亮的值?



我可以检查哪些组件以及如何检查?

解决方案

不幸的是,这只是一种解决方法(但我会尽快编写更多内容),但是这篇帖子指出我只是工具->选项->调试器-> GDB 禁用加载系统GDB漂亮打印机 >

此行为是其中的归档的错误 QtCreator 3.0



现在似乎对我有用!



编辑:尽管QtCreator 3.0的错误跟踪器指出错误已得到修复,但该错误实际上仍存在于更高版本中-至少从v3.1.2开始。幸运的是,可以采用相同的建议解决方法。


I have the same problem as described in Variables in Locals and Expressions not accessible in QT Creator but I want to find a way how to "repair" Qt Creator showing default composite types like std::string in the debugging window again.

I've updated from Creator 2.8 to 3.0 via a dist upgrade (fedora 18=>20) and I know things can go wrong there but I really want to avoid re-installing the whole OS just for Qt Creator.

Is there any way to make the Creator more verbose or does it write to a log file?

Is Qt Creator 3.0 known to show nice values for composite types anyway?

What components can I check and how?

解决方案

Unfortunately it's only a workaround (but I will write more as soon as possible) but this post pointed me to just disable "Load system GDB pretty printers" in Tools->Options->Debugger->GDB

This behavior is a filed bug in QtCreator 3.0

seems to work for me now!

EDIT: Although the bug tracker for QtCreator 3.0 says the bug has been fixed, the bug actually persists in later versions - at least as of v3.1.2 . Fortunately the same suggested workaround applies.

这篇关于如何解决Qt Creators变量“<不可访问>”。行为?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆