Public bug reported:

When opening a large (368 page) .doc document), abiword crashes with a
segmentation fault, as detailed in the attached gdb full readout.  The
document only contains formatted text with footnotes and no unusual
symbols; it opens fine in Libreoffice Writer.

 I cannot, unfortunately, attach the .doc document at the moment, as it
is a personal thesis.

I am running Ubuntu 12.04.1, 32 bit (Xubuntu).
Kernel: 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:32:50 UTC 2012 i686 i686 
i386 GNU/Linux

Abiword default version: 2.9.2+svn20120213-1

Typical error, documented in the gdb attachment below:

Program received signal SIGSEGV, Segmentation fault.
0x0037f3c4 in fl_DocSectionLayout::getTopMargin (this=0x59524101) at 
fl_SectionLayout.cpp:2421

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: abiword 2.9.2+svn20120213-1
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic i686
ApportVersion: 2.0.1-0ubuntu14
Architecture: i386
Date: Mon Nov  5 19:06:23 2012
ExecutablePath: /usr/bin/abiword
InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: abiword
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: abiword (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 precise

** Attachment added: "full gdb analysis: backtrace etc as per guidelines"
   
https://bugs.launchpad.net/bugs/1075295/+attachment/3424858/+files/gdb-abiword.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075295

Title:
  SIGSEGV, Segmentation fault on loading large .doc file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1075295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to