Page 1 of 1

CRITICAL: msn_object_new_from_string...

Posted: Sun Oct 22, 2006 4:19 pm
by seh2000
Hi!

Installed Adium X 0.89.1 on my MBP with 10.4.8 and everything seams to be fine but in Console I keep seeing the below error messages!
Anyone have an idea why I keep getting those errors? What to do to fix it?

Thanks- Steen

PS.: Forgive if I am not too technical, but I am new to the MAC world...



** (process:910): CRITICAL **: msn_object_new_from_string: assertion `!strncmp(str, "<msnobj ", 8)' failed

** (process:910): CRITICAL **: msn_object_new_from_string: assertion `!strncmp(str, "<msnobj ", 8)' failed

** (process:910): CRITICAL **: msn_object_new_from_string: assertion `!strncmp(str, "<msnobj ", 8)' failed

** (process:910): CRITICAL **: msn_object_new_from_string: assertion `!strncmp(str, "<msnobj ", 8)' failed

** (process:910): CRITICAL **: msn_object_new_from_string: assertion `!strncmp(str, "<msnobj ", 8)' failed

** (process:9115): CRITICAL **: file /Users/evands/libgaim/libgaim/src/protocols/msn/slplink.c: line 585 (msn_slplink_process_msg): should not be reached

Posted: Mon Oct 23, 2006 4:51 pm
by seh2000
Any of you out there got an idea to why I have this error?

Re: CRITICAL: msn_object_new_from_string...

Posted: Fri Jun 13, 2008 7:01 pm
by rand
Noticed the same error last night :

Jun 12 23:58:07 it'sacomputername [0x0-0x28028].com.adiumX.adiumX[391]: ** (process:391): CRITICAL **: file /Users/evands/pidgin-for-adium/libpurple/protocols/msnp9/slplink.c: line 603 (msn_slplink_process_msg): should not be reached

using Adium 1.2.5 Monday 28th April 2008. Just checked for updates, none through built in updater.

Easy to see why the error is there, just posting because not sure what version the previous poster was using, it may have been an older version and the issue hasn't been fixed.

Keep up the great work.

Edit : just noticed the other poster was from 2006. Guess the problem is still around =)

Re: CRITICAL: msn_object_new_from_string...

Posted: Fri Jun 13, 2008 9:58 pm
by Catfish_Man
Some warnings logged to console have been fixed in 1.3; in general though, if it's not behaving badly, don't worry about it.