gedit crashed with SIGSEGV

Bug #911772 reported by Sasa Paporovic on 2012-01-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)

Bug Description

I have opended a kernel.log which has so much entries that gedit was not able to reach then end of the document.

On closing this fiel gedit SIGSEV was catched by apport deamon.

I would like to attach the kernel log for reproducing purposes, but it has a size of 1.6GB, so attaching seems not to be indicated.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Jan 4 14:32:02 2012
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gedit /var/log/apport.log
 Segfault happened at: 0x440a08: mov 0x10(%rax),%rdi
 PC (0x00440a08) ok
 source "0x10(%rax)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gedit
 #0 0x0000000000440a08 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffd1e5b418
StacktraceTop: ?? ()
Title: gedit crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2011-12-31 (3 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare

Sasa Paporovic (melchiaros) wrote :
visibility: private → public

 #0 info_bar_set_progress (tab=<optimized out>, size=6, total_size=1) at gedit-tab.c:894
         __PRETTY_FUNCTION__ = "info_bar_set_progress"
 Cannot access memory at address 0x7fffd1e5b458
StacktraceTop: info_bar_set_progress (tab=<optimized out>, size=6, total_size=1) at gedit-tab.c:894

Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gedit (Ubuntu):
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers