[ ayttm-Bugs-2725049 ] segfault

Bugs item #2725049, was opened at 2009-04-01 18:44
Message generated for change (Comment added) made by siddheshp
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=550744&aid=2725049&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: Jabber
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: quinq (quinq)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault

Initial Comment:
I activated jabber debugging in option, and then tried to connect.
Here is error log:

Ayttm version 0.5.0-82
GTK+ version 2.14.7
Features:
Operating system: Linux 2.6.28.5-20090215 (x86_64)
C Library: GNU libc 2.9
Signal: 11
--
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fe5606c4790 (LWP 18902)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007fe5601c22e5 in waitpid () from /lib/libpthread.so.0
#0  0x00007fe5601c22e5 in waitpid () from /lib/libpthread.so.0
#1  0x0000000000446362 in ?? ()
#2  <signal handler called>
#3  0x00007fe556cd1402 in j_on_state_handler () from /usr/lib/ayttm/jabber.so
#4  0x00007fe55995bba3 in ?? () from /usr/lib/libexpat.so.1
#5  0x00007fe55995cae4 in ?? () from /usr/lib/libexpat.so.1
#6  0x00007fe559954f91 in XML_ParseBuffer () from /usr/lib/libexpat.so.1
#7  0x00007fe556cd2d19 in jab_poll () from /usr/lib/ayttm/jabber.so
#8  0x00007fe556cd21c2 in jabber_callback_handler ()
   from /usr/lib/ayttm/jabber.so
#9  0x0000000000442261 in ?? ()
#10 0x00007fe55db25e4a in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#11 0x00007fe55db29510 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007fe55db299dd in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0x00007fe55f2dd737 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x000000000041b4fd in main ()
Kill the program being debugged? (y or n) [answered Y; input not from terminal]


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

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2009-05-20 01:26

Message:
This should be fixed in the latest ayttm release since the connection code
has undergone a lot of change. Please reopen if the problem exists.

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

Comment By: Siddhesh Poyarekar (siddheshp)
Date: 2009-04-01 20:34

Message:
Thanks for submitting this. I'll need more info on this. Can you do the
following:

Start ayttm from a terminal and capture the debug output that it dumps on
execution right up to the crash. The command to do this on the terminal
would be:

ayttm 2> ayttm.debug.out

And then attach ayttm.debug.out here.

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

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

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects