GNOME Bugzilla – Bug 432899
crash in XChat-GNOME IRC Chat:
Last modified: 2007-04-25 13:34:30 UTC
What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.18.1 2007-04-10 (Foresight Linux) BugBuddy Version: 2.18.1 System: Linux 2.6.20.7-1.smp.gcc3.4.x86.i686 #1 SMP Fri Apr 20 15:27:04 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Foresight Icon Theme: Tango Memory status: size: 45539328 vsize: 45539328 resident: 24985600 share: 11739136 rss: 24985600 rss_rlim: 4294967295 CPU usage: start_time: 1177406562 rtime: 134 utime: 110 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/xchat-gnome' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226339536 (LWP 3850)] (no debugging symbols found) 0xb7f0a410 in ?? ()
+ Trace 130206
Thread 1 (Thread -1226339536 (LWP 3850)): #-1 0xb7f0a410 in ?? () No symbol table info available. #-1 0xb7f0a410 in ?? () ----------- .xsession-errors --------------------- GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Backtrace limit of 200 exceeded /usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file: Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 421973 ***