xpdf.real crashed with SIGSEGV in GooHash::hash()

[avinas]

opening pdf and crasing

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xpdf 3.02-21build1
ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Wed Feb 13 22:13:32 2013
ExecutablePath: /usr/bin/xpdf.real
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: xpdf.real -title Xpdf:\ /home/pirmas/Downloads/Umberto.Eco.-.Prahos.kapines.2012.LT.pdf /home/pirmas/Downloads/Umberto.Eco.-.Prahos.kapines.2012.LT.pdf
ProcCwd: /home/pirmas
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f397e97d420 <_ZN7GooHash4hashEP9GooString>: mov 0x20(%rsi),%r8
 PC (0x7f397e97d420) ok
 source "0x20(%rsi)" (0x01010021) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xpdf
StacktraceTop:
 GooHash::hash(GooString*) () from /tmp/tmp_ty2d8/usr/lib/x86_64-linux-gnu/libpoppler.so.19
 GooHash::find(GooString*, int*) () from /tmp/tmp_ty2d8/usr/lib/x86_64-linux-gnu/libpoppler.so.19
 GooHash::lookup(GooString*) () from /tmp/tmp_ty2d8/usr/lib/x86_64-linux-gnu/libpoppler.so.19
 GlobalParams::getResidentUnicodeMap(GooString*) () from /tmp/tmp_ty2d8/usr/lib/x86_64-linux-gnu/libpoppler.so.19
 GlobalParams::getUnicodeMap2(GooString*) () from /tmp/tmp_ty2d8/usr/lib/x86_64-linux-gnu/libpoppler.so.19
Title: xpdf.real crashed with SIGSEGV in GooHash::hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #943195, 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.