[Ayttm-users] [Bug #3001] ayttm crashes randomly everytime i run

[nobody]

=================== BUG #3001: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3001&group_id=3592

Changes by: Philip S Tellis <address@hidden>
Date: Sun 03/30/2003 at 12:38 (Asia/Calcutta)

------------------ Additional Follow-up Comments ----------------------------
This appears to be a gtk+ problem, although I cannot be 
certain.  The bactrace shows no reference to actual code in 
ayttm, so we can't identify where it comes from exactly.  
Could you run ayttm under valgrind and get an error log 
from there? 

Philip



=================== BUG #3001: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: Ayt the messenger            
Submitted on: Sun 03/30/2003 at 10:10
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  0.2.3-pre62                 

Summary:  ayttm crashes randomly everytime i run

Original Submission:  ayttm crashed everytime. i run it for some time and 
happens at any instant.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 03/30/2003 at 12:38       By: bluesmoon
This appears to be a gtk+ problem, although I cannot be 
certain.  The bactrace shows no reference to actual code in 
ayttm, so we can't identify where it comes from exactly.  
Could you run ayttm under valgrind and get an error log 
from there? 

Philip


CC list is empty


File Attachments
****************

-------------------------------------------------------
Date: Sun 03/30/2003 at 10:10  Name: ayttm-crash-log-2003-03-30-10-11-54.txt  
Size: 1KB   By: None

http://savannah.nongnu.org/bugs/download.php?group_id=3592&amp;bug_id=3001&amp;bug_file_id=372


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=3001&group_id=3592