[ ayttm-Bugs-2926098 ] crash on AYTTM logging into MSN

Bugs item #2926098, was opened at 2010-01-05 14:29
Message generated for change (Comment added) made by siddheshp
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=550744&aid=2926098&group_id=77614

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MSN
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Siddhesh Poyarekar (siddheshp)
Summary: crash on AYTTM logging into MSN

Initial Comment:
I'm using AYTTM 0.6.1.0 on ubuntu karmic koala. I compiled the package with checkinstall on one box, and have tried it on two. On both i get a crash when logging onto MSN- on both, the terminal i start it from reads 

the crash log reads

Ayttm version 0.6.1-0
GTK+ version 2.18.3
Features:
Operating system: Linux 2.6.31-16-generic (i686)
C Library: GNU libc 2.10.1
Signal: 11
--
when run it with x forwarding, and signal 6 locally.

on a local session, the terminal also gives me this error  output
http://pastebin.com/f65f8b5



----------------------------------------------------------------------

>Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2010-01-05 20:13

Message:
OK, that is better... I guess. Could you repeat this with a regular
make/make install? The checkinstall method seems to be stripping out debug
info.

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-01-05 20:11

Message:
I'm not keeping a full repository- merely grabbing snapshots as needed - i
don't think this one works either though. Its not buffer overflowing (yay!)
on the other hand.. it seems to segfault
Thread 4 (Thread 0xb6aeeb70 (LWP 20908)):
#0  0x00aa7868 in ?? () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.                          
#1  0x080a993d in ?? ()                                  
No symbol table info available.                          
#2  0x005dc37f in ?? () from /lib/libglib-2.0.so.0       
No symbol table info available.                          
#3  0x00b2480e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.                                          
#4  0x00c047ee in clone () from /lib/tls/i686/cmov/libc.so.6             
No symbol table info available.                                          

Thread 1 (Thread 0xb7fda730 (LWP 20901)):
#0  0x007f3422 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00b28e15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2  0x0058cc5e in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#3  0x0058cfe6 in g_async_queue_pop () from /lib/libglib-2.0.so.0
No symbol table info available.
#4  0x080a9d0e in ay_connection_connect ()
No symbol table info available.
#5  0x00aa5f1b in ext_msn_connect () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.
#6  0x00aacabc in msn_http_request () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.
#7  0x00aadfd0 in ?? () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.
#8  0x00aa9acd in msn_connection_pop_callback () from
/usr/local/lib/ayttm/msn2.so
No symbol table info available.
#9  0x00aa9b77 in msn_got_response () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.
#10 0x00aa7ed2 in ?? () from /usr/local/lib/ayttm/msn2.so
No symbol table info available.
#11 0x0808a28b in ?? ()
No symbol table info available.
#12 0x005e8dab in ?? () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#13 0x005b1e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
No symbol table info available.
#14 0x005b5730 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#15 0x005b5b9f in g_main_loop_run () from /lib/libglib-2.0.so.0
No symbol table info available.
#16 0x0110d419 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#17 0x0805efcc in main ()
No symbol table info available.



----------------------------------------------------------------------

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2010-01-05 19:53

Message:
Sheesh, that was ugly. I've put in the fix. Could you please verify that it
works? All you have to do is this:

1) From your git repository clone, do a "git pull"
2) Rebuild
3) Test

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-01-05 19:53

Message:
i've included a error log with the latest GIT and checkinstall, and the
release and checkinstall as well - hopefully this should help determine if
checkinstall was a source of problems, though i don't think so. 

checkinstall basically simplifies sharing a compiled app by making a
package of it. its essentially a make install + quick and dirty packaging -
it may not be up to debian standards, but i use it with most apps i compile
for easy installation and removal.. 

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-01-05 19:42

Message:
this is the crash log for the latest GIT version, using the 'normal' way of
installing from source - ./ configure, make, make install

----------------------------------------------------------------------

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2010-01-05 19:15

Message:
Ok, thanks for that information. As for gdb, all you have to do is run
ayttm under gdb:

gdb ayttm

Once you're at the gdb prompt, type the 'run' command to start ayttm and
then let it crash. You'll get the gdb prompt back once it crashes. When you
get that, type:

thread apply all bt full

and then paste the entire screen dump on this ticket either as a comment
or an attachment.

As for checkinstall, I'm not sure what it does, but I hope it does a 'make
install' as well since otherwise you'll be using the new core and old
plugins :)

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-01-05 19:09

Message:
How do i run gdb? 

as for the git repo version (i was rather hoping it would work ;p), once i
worked out it broke checkinstall (another bug report i guess? ;) ) and how
to fix it (strip the spaces in the description), and got it running,it also
crashed in a similar way.



----------------------------------------------------------------------

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2010-01-05 18:38

Message:
Could you also test with code from our git repository?

git://ayttm.git.sourceforge.net/gitroot/ayttm/ayttm

----------------------------------------------------------------------

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2010-01-05 17:46

Message:
Thanks, this looks like a nice find. Could you do this:

1) run ayttm from gdb
2) wait for crash
3) send a full backtrace using "thread apply all bt full"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=550744&aid=2926098&group_id=77614

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev