Bug #241
im_server crashing when a protocol goes online
| Status: | Closed | Start: | 04/11/2009 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | im_server | Spent time: | 1.00 hour | |
| Target version: | 0.9.2 | Estimated time: | 1.00 hour | |
| Operating System: |
Description
As of r881 there's a bug, here's how you can reproduce it:
0. Configure at least one account, I have configure a gtalk account but I think the issue can be reproduced with other protocols as well.
1. Start im_server
2. Change the status to Available for gtalk.
3. Look at how the server crashes :)
I will attach the backtrace...
History
Updated by Pier Luigi Fiorini over 1 year ago
[Switching to team /boot/common/servers/im_server (1553) thread im_server (1553)]
0x00410c60 in entry_ref::operator= () from /boot/system/lib/libbe.so
(gdb) bt
#0 0x00410c60 in entry_ref::operator= () from /boot/system/lib/libbe.so
#1 0x00278550 in IM::Contact::SetTo (this=0x0, contact=@0x7ffee7b4)
at libim/Contact.cpp:80
#2 0x0023bdbe in IM::Server::MessageFromProtocols (this=0x7ffeee0c,
msg=0x1800fd70) at im_server.cpp:1459
#3 0x0023863d in IM::Server::Process (this=0x7ffeee0c, msg=0x1800fd70)
at im_server.cpp:886
#4 0x002356b2 in IM::Server::MessageReceived (this=0x7ffeee0c, msg=0x1800fd70)
at im_server.cpp:436
#5 0x0033ae7f in BLooper::DispatchMessage () from /boot/system/lib/libbe.so
#6 0x00331771 in BApplication::DispatchMessage ()
from /boot/system/lib/libbe.so
#7 0x0033c7ed in BLooper::task_looper () from /boot/system/lib/libbe.so
#8 0x0032fedd in BApplication::Run () from /boot/system/lib/libbe.so
#9 0x002340f4 in IM::Server::Server (this=0x7ffeee0c) at im_server.cpp:155
#10 0x00250a04 in main (numarg=1, argv=0x7ffef538) at im_server_main.cpp:94
