GNOME Bugzilla – Bug 318060
too long string loaded in gEdit, it crashed
Last modified: 2006-01-07 11:24:29 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 2.8.1 Gnome-Distributor: Red Hat, Inc Synopsis: too long string loaded in gEdit, it crashed Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...`shared object read from target memory' has disappeared; keeping its symbols. (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)...[Thread debugging using libthread_db enabled] [New Thread -1213053248 (LWP 5132)] [New Thread -1228719184 (LWP 5136)] [Thread debugging using libthread_db enabled] [New Thread -1213053248 (LWP 5132)] [New Thread -1228719184 (LWP 5136)] [Thread debugging using libthread_db enabled] [New Thread -1213053248 (LWP 5132)] [New Thread -1228719184 (LWP 5136)] [New Thread -1228452944 (LWP 5135)] [New Thread -1228104784 (LWP 5134)] [New Thread -1217614928 (LWP 5133)] (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)...0xb7fa5402 in __kernel_vsyscall ()
+ Trace 63388
Thread 5 (Thread -1217614928 (LWP 5133))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-05 22:08 UTC ------- Bugreport moved from gnome-utils / gdict to gedit / general Unknown version 2.8.1 in product gedit. Setting version to "2.8.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was waah.waah@waah.com.
Seems to be a dupolicate of bug #134682, but with better backtrace
This is an out-of-memory problem in pango, but as Luis said we can consider it a duplicate of bug #134682 *** This bug has been marked as a duplicate of 134682 ***