You are not logged in.
I have just installed Freetalk. It is great, but i have problems with it. When i run it, it outputs lots of debug stuff.
anonymous@jabber.example.com> yet_another_anonymous@jabber.example.com Hi!
LM-LOG-0x200:
SEND:
LM-LOG-0x200: -----------------------------------
LM-LOG-0x200: <message type="chat" to="yet_another_anonymous@jabber.example.com" id="some_id"> <body>Hi!</body>
</message>
LM-LOG-0x200: -----------------------------------
Looks like all these LM-LOG-0x... are produced by loudmouth. I have downloaded PKGBUILD for loudmouth with ABS, but it looks like debug output is already disabled. Changing LM_DEBUG environment variable (it is unset by default) does not help. How can i disable this debug output? Have you similar problems?
Last edited by anonymous (2009-07-06 02:22:49)
Offline
Even if you don't know how to solve it, please, tell me if you have the same problem.
Offline
I have just tried to rebuild loudmouth and freetalk. Rebuilding loudmouth doesn't help. I have configured it with --with-debug=NO, but i think it affect only debug symbols. Also, it has perlxml in it's dependencies, but in fact it builds without it well.
Freetalk fails to build with this message:
callbacks.cc: In function 'LmHandlerResult ft_msg_msg_handler(LmMessageHandler*, LmConnection*, LmMessage*, void*)':
callbacks.cc:156: error: assignment of read-only location '* strchr(from, 47)'
Maybe maintainer has built it with another version of loudmouth.
Offline
Anybody, please, just check if you have the same problem. Simply install freetalk, run it from command line, type your JID and password into it, then /quit to quit. Then tell me if you have these LM-LOG messages.
Offline
Offline
I have searched in the loudmouth sources. I have found these lines in lm-connection.c:
g_log (LM_LOG_DOMAIN, LM_LOG_LEVEL_NET, "\nSEND:\n");
g_log (LM_LOG_DOMAIN, LM_LOG_LEVEL_NET,
"-----------------------------------\n");
g_log (LM_LOG_DOMAIN, LM_LOG_LEVEL_NET, "%s\n", str);
g_log (LM_LOG_DOMAIN, LM_LOG_LEVEL_NET,
"-----------------------------------\n");
So now i know that it is output of loudmouth, not freetalk. Now i need to disable g_log (http://library.gnome.org/devel/glib/2.2 … html#g-log) output. I have searched in glib documentation (http://library.gnome.org/devel/glib/sta … nning.html) but have not found any environment variable or something like this that can help.
And again, --enable-debug=no does not help.
Update: Have just found this fix: http://github.com/engineyard/loudmouth/ … b9c1e70ecb. Looks like i need to apply this patch or build git version. The problem is that loudmouth use g_log_default_handler(http://library.gnome.org/devel/glib/unstable/glib-Message-Logging.html#g-log-default-handler) when debug is disabled at compiling. As said in documentation "It outputs the message to stderr or stdout and if the log level is fatal it calls abort()." I have searched in lm-debug too, but i have never programmed with glib so i have not found the problem.
And if anyone is interested, i have found something about current state of loudmouth: http://groups.google.com/group/loudmout … ebb8dc9e8e
Here loudmouth is looking for new maintainer and some people from Engine Yard says that he is currently working on it. So i think that http://github.com/engineyard/loudmouth/ is now the primary repository for loudmouth.
Update: i have pathed loudmouth 1.4.3 and now it works fine. Hope the next version will be already fixed, so i won't need to fix it by hand.
Last edited by anonymous (2009-07-06 04:22:12)
Offline