rastertoqpdl crashed with SIGSEGV in memcpy()

Bug #268512 reported by Rajivmudgal
8
Affects Status Importance Assigned to Milestone
splix (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: splix

fully updated 810

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/cups/filter/rastertoqpdl
NonfreeKernelModules: nvidia
Package: splix 2.0.0~rc2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: ML-1610 2 shashwat Untitled1 1 Resolution=300dpi\ InputSlot=Auto\ PageSize=Letter\ job-uuid=urn:uuid:e7a9e413-e241-3eb6-7cc1-caf6dd3cb07f
ProcEnviron:
 PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin
 LANG=en_IN.UTF8
Signal: 11
SourcePackage: splix
Stacktrace:
 #0 0xb7c8bb11 in memcpy () from /lib/tls/i686/cmov/libc.so.6
 #1 0x0804beba in ?? ()
 #2 0x0804f840 in ?? ()
 #3 0xb7ee54ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 #4 0xb7cf464e in clone () from /lib/tls/i686/cmov/libc.so.6
StacktraceTop:
 memcpy () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: rastertoqpdl crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.27-2-generic i686
UserGroups:

Revision history for this message
Rajivmudgal (rajiv-mudgal) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memcpy () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()
start_thread () from /lib/tls/i686/cmov/libpthread.so.0
clone () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 268510, so it 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. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.