在mongooseim中,对应用程序调试器中的i:im()的调用失败 [英] Call to i:im() in application debugger failed in mongooseim
问题描述
似乎调用了 im()
。调用 ./ bin / mongooseim debug
外壳后失败,并显示消息在应用程序调试器中调用i:im / 0失败。但是,当我执行典型的Erlang外壳程序时,它将正确打开窗口。知道为什么吗?
It seems invoking im()
. after invoking ./bin/mongooseim debug
shell fails with message "call to i:im/0 in application debugger fails". However, when I do it typical Erlang shell, it opens up the window correctly. Any idea why ?
推荐答案
启动调试器图形界面可能会失败的原因有几个:
There is several reasons starting debugger graphical interface could fails:
- 您正在调试远程服务器,并且该服务器无法通过SSH在本地计算机上显示其UI。
- 您缺少对上下文中某些Erlang组件的访问权限
例如,我在本地计算机上尝试运行,效果很好:
As an example, I tried on my local computer and it worked fine:
$ ./ejabberdctl debug
...
Erlang/OTP 17 [erts-6.4] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:true]
Eshell V6.4 (abort with ^G)
(ejabberd@localhost)1> i:im().
<0.464.0>
它甚至与 ejabberd二进制安装程序,该文件在 INSTALLER_DIR / lib /
中添加了Erlang R17B-5的调试器组件之后。
您需要添加到二进制安装程序以使用图形调试器的组件是: debugger
和 wx
。只需复制这两个目录即可。
It even worked with ejabberd binary installer after adding the debugger component for Erlang R17B-5 in INSTALLER_DIR/lib/
.
The component you need to add to binary installer to use the graphical debugger are: debugger
and wx
. Just copied those two dir and it worked.
这篇关于在mongooseim中,对应用程序调试器中的i:im()的调用失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!