evince crashed with SIGSEGV in SampledFunction::transform()q

[Sebastian Kuzminsky]

Binary package hint: evince

The attached pdf crashes evince on my laptop.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/evince
Package: evince 2.23.91-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: evince file:///tmp/2008SPYSupplement.pdf
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evince
StacktraceTop:
 SampledFunction::transform ()
 StitchingFunction::transform ()
 GfxAxialShading::getColor ()
 Gfx::doAxialShFill () from /usr/lib/libpoppler.so.3
 Gfx::doShadingPatternFill ()
Title: evince crashed with SIGSEGV in SampledFunction::transform()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #185226. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Pedro Villavicencio (pedro)]

It works fine for me with intrepid in a i386 system this is maybe only amd64 related, can you get a backtrace as described here: http://wiki.ubuntu.com/DebuggingProgramCrash ; thanks a lot.

[Sebastian Kuzminsky (seb-highlab)]

Pedro Villavicencio wrote:
> It works fine for me with intrepid in a i386 system this is maybe only
> amd64 related, can you get a backtrace as described here:
> http://wiki.ubuntu.com/DebuggingProgramCrash ; thanks a lot.
>
> ** Changed in: evince (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete

Thanks for looking at this.

I installed the evince-dbgsym package, but the version of evince there
wont run. Maybe there's some step in the debugging setup that's not on
the DebuggingProgramCrash page?

I'm guessing you're not interested in a backtrace of the standard evince?

--
Sebastian Kuzminsky
"Much of what we learned from the sense of touch was unscientific
prejudice, which must be rejected if we are to have a true picture
of the world." -- Bertrand Russell

[Sebastian Kuzminsky (seb-highlab)]

Problem still happens with evince 2.23.92-0ubuntu1.

> 0 seb@water /home/seb> dpkg -l evince{,-dbgsym}
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-=========================-=========================-==================================================================
> ii evince 2.23.92-0ubuntu1 Document (postscript, pdf) viewer
> ii evince-dbgsym 2.23.92-0ubuntu1 debug symbols for package evince
> 0 seb@water /home/seb> ldd /usr/lib*/debug/usr/bin/evince
> /usr/lib64/debug/usr/bin/evince:
> /usr/bin/ldd: line 117: /usr/lib64/debug/usr/bin/evince: cannot execute binary file
> /usr/lib/debug/usr/bin/evince:
> /usr/bin/ldd: line 117: /usr/lib/debug/usr/bin/evince: cannot execute binary file
> 1 seb@water /home/seb> file /usr/lib*/debug/usr/bin/evince
> /usr/lib64/debug/usr/bin/evince: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
> /usr/lib/debug/usr/bin/evince: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
> 0 seb@water /home/seb> /usr/lib/debug/usr/bin/evince
> bash: /usr/lib/debug/usr/bin/evince: cannot execute binary file
> 126 seb@water /home/seb> /usr/lib64/debug/usr/bin/evince
> bash: /usr/lib64/debug/usr/bin/evince: cannot execute binary file

What am I doing wrong when trying to run the dbgsym programs?

[Brian Murray (brian-murray)]

evince did not crash for me using the test document provided on an amd64 machine.

[Sebastian Kuzminsky (seb-highlab)]

It crashed on my amd64 machine after paging down a couple of times.

[Sebastian Kuzminsky (seb-highlab)]

I have a repeatable crash with evince 2.24.0 (poppler 0.8.7) on Ubuntu Intrepid alpha 6, on an amd64 CPU (Intel Core 2 Duo). To crash it i page-down in this PDF a couple of times: <http://launchpadlibrarian.net/17355619/2008SPYSupplement.pdf>

Here's the Ubuntu bug that I originally filed: <https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/267324>

The Ubuntu bug includes a stacktrace and some other hopefully useful stuff.

Let me know what I can do to help from here...

[Sebastien Bacher (seb128)]

do you still get the issue? could you get a debug stacktrace?

[Albert Astals Cid (aacid)]

Should be fixed in poppler 0.10.0 due for release in October 9th

If you can try poppler from git master as of *now* and tell me if it still crashes it would be nice. I made it not crash here but a second opinion is always welcome.

[Sebastian Kuzminsky (seb-highlab)]

I still get the crash.

I've attached a crashdump (from the regular evince package) to this
email, because I couldnt figure out how to get apport to attach it to an
existing bug.

I also couldnt figure out how to run the executable from evince-dbgsym
and i've attached a log of my attempt.

[Sebastien Bacher (seb128)]

don't attach crash file to bug they can contain sensible informations and should be sent using apport, you can close one of the bug as duplicate then, you need libpoppler3-dbgsym to get a debug stacktrace and use gdb on evince, gdb will use the debug symbols automatically

[Sebastian Kuzminsky (seb-highlab)]

Thanks for the info, i've attached a backtrace.

[Sebastien Bacher (seb128)]

the crash is a libpoppler one, since you are able to trigger the issue could you open the bug on bugs.freedesktop.org too where people writting the software will read it too rather than only ubuntu bug triages?

[Sebastian Kuzminsky (seb-highlab)]

Sebastien Bacher wrote:
> the crash is a libpoppler one, since you are able to trigger the issue
> could you open the bug on bugs.freedesktop.org too where people writting
> the software will read it too rather than only ubuntu bug triages?
>
> ** Changed in: poppler (Ubuntu)
> Sourcepackagename: evince => poppler
> Status: Incomplete => New

Here it is:

<https://bugs.freedesktop.org/show_bug.cgi?id=17852>

--
Sebastian Kuzminsky
Distances obtained as the speed of light multiplied by a cosmological
time interval have no direct physical significance.
<http://en.wikipedia.org/wiki/Observable_universe>

[Greg Grossmeier (greg.grossmeier)]

From upstream (a request for confirmation of the fix)
----
Should be fixed in poppler 0.10.0 due for release in October 9th

If you can try poppler from git master as of *now* and tell me if it still
crashes it would be nice. I made it not crash here but a second opinion is
always welcome.
----

[Pedro Villavicencio (pedro)]

fixed upstream, thanks for reporting.

[DSHR (s-heuer)]

Will the new poppler version make it into intrepid? I encounter the same bug in intrepid beta.

[Sebastien Bacher (seb128)]

the new version has been uploaded to jaunty now

[DSHR (s-heuer)]

Seems to be fixed for me in jaunty ...

[Albert Astals Cid (aacid)]

*** Bug 21491 has been marked as a duplicate of this bug. ***