Bug 618851 - [abrt] crash in gedit-1:2.30.2-1.fc13: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gedit-1:2.30.2-1.fc13: Process /usr/bin/gedit was killed by s...
Keywords:
Status: CLOSED DUPLICATE of bug 627772
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cce21a75a3c5b5d34d13a9ede1f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-27 21:11 UTC by laurenthoudijk
Modified: 2010-11-09 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:33:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (25.41 KB, text/plain)
2010-07-27 21:12 UTC, laurenthoudijk
no flags Details

Description laurenthoudijk 2010-07-27 21:11:58 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gedit
comment: I opened a very large text/script, I had to replace a string with a very high frequency (200+) with some other string, it seemed like it couldn't handle the high load and crashed.
component: gedit
crash_function: _gtk_text_btree_get_chars_changed_stamp
executable: /usr/bin/gedit
global_uuid: cce21a75a3c5b5d34d13a9ede1f162b1e4b1ba54
kernel: 2.6.33.5-112.fc13.x86_64
package: gedit-1:2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 laurenthoudijk 2010-07-27 21:12:01 UTC
Created attachment 434850 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 16:33:26 UTC

*** This bug has been marked as a duplicate of bug 627772 ***

Comment 3 Karel Klíč 2010-11-09 16:33:26 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #627772.

Sorry for the inconvenience.


Note You need to log in before you can comment on or make changes to this bug.