evince crashed with SIGSEGV in __strchr_sse2()

Bug #884928 reported by Moritz Naumann on 2011-11-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)

Bug Description

This is likely a duplicate of #879926 - but it's hjard to tell for sure at this point, and I don't want to spoil possibly use debugging info. I'm not sure how to reproduce this bug, it must have happened when I was downloading and opening a PDF from Firefox. It's probably so that I had multipld PDF document open at this time and it's possibly so that I downloaded the same document multiple times. Evince works fine normally, I'm not sure what was different here.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 1 21:20:43 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.0.0-13-generic root=/dev/mapper/vg0-hostname ro quiet splash vt.handoff=7
 PATH=(custom, user)
 Segfault happened at: 0x7f91978edc2a <__strchr_sse2+26>: movdqa (%rdi),%xmm0
 PC (0x7f91978edc2a) ok
 source "(%rdi)" (0x00000110) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
 __strchr_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:33
 g_param_spec_pool_lookup () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: evince crashed with SIGSEGV in __strchr_sse2()
UpgradeStatus: Upgraded to oneiric on 2011-10-21 (11 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

Moritz Naumann (mnaumann) wrote :

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #879926, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers