foomatic-rip crashed with SIGSEGV in Perl_csighandler()

Bug #217662 reported by nikolaj.kuebler on 2008-04-15
Affects Status Importance Assigned to Milestone
perl (Ubuntu)

Bug Description

Binary package hint: foomatic-filters

I would like to print out a PDF.
The printer doesn't receive any data, I think.

ProblemType: Crash
Architecture: i386
Date: Tue Apr 15 12:26:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/foomatic-rip
InterpreterPath: /usr/bin/perl
NonfreeKernelModules: fglrx
Package: foomatic-filters 3.0.2-20071204-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/perl /usr/lib/cups/filter/foomatic-rip 70 niko Acropjocjh 1 media=A4\ sides=one-sided\ finishings=3\ number-up=1\ InputSlot=Tray1\ PageSize=A4\ Duplex=DuplexNoTumble\ job-uuid=urn:uuid:aedee819-36bc-3a32-7a00-f2f7a9786b4e
Signal: 11
SourcePackage: foomatic-filters
Stacktrace: #0 0x080b49f7 in Perl_csighandler ()
StacktraceTop: Perl_csighandler ()

Title: foomatic-rip crashed with SIGSEGV in Perl_csighandler()
Uname: Linux 2.6.24-16-generic i686
 Segfault happened at: 0x80b49f7 <Perl_csighandler+23>: testb $0x1,0xa30(%eax)
 PC (0x080b49f7) ok
 source "$0x1" ok
 destination "0xa30(%eax)" (0x00000a30) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

Till Kamppeter (till-kamppeter) wrote :

In Intrepid foomatic-rip is replaced by a new generation which is not written in Perl any more. It is written in C and so it does not need to rely on the Perl infrastructure any more. So this problem should disappear in Intrepid.

In general, this segfault happens in code of the Perl interpreter, so this must be a bug in Perl. Moving to Perl ...

Kees Cook (kees) on 2009-09-16
description: updated

Till, is this problem now fixed?

Changed in perl (Ubuntu):
status: New → Incomplete
Till Kamppeter (till-kamppeter) wrote :

This is from the old Foomatic 3.x generation written in Perl. We are using 4.x currently which is written in C. Closing ...

Changed in perl (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers