pdfedit crashed with SIGSEGV in *__GI___libc_free() with specific file

Bug #539652 reported by Muelli on 2010-03-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pdfedit (Ubuntu)

Bug Description

Binary package hint: pdfedit

Just opening pdfedit with the file provided makes it crash

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 16 16:31:53 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pdfedit
Package: pdfedit 0.4.3-1
ProcCmdline: pdfedit pdfedit-crash.pdf
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
 Segfault happened at: 0x7f7f91629c3d <*__GI___libc_free+29>: mov -0x8(%rdi),%rsi
 PC (0x7f7f91629c3d) ok
 source "-0x8(%rdi)" (0x4e004500430041) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pdfedit
 *__GI___libc_free (mem=0x4e004500430049) at malloc.c:3709
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: pdfedit crashed with SIGSEGV in *__GI___libc_free()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin netdev plugdev powerdev scanner tty vboxusers video

visibility: private → public
Andy Branscomb (droolingsheep) wrote :

I get these errors when I attempt to reproduce this bug.

abransco@toledo-linux:~/Downloads$ pdfedit pdfedit-crash.pdf
Error: PDF file doesn't contain proper header
2:KERNEL:cxref.cc:CXref:46: Unable to parse xref table. errorCode=11
Segmentation fault (core dumped)

Ubuntu Lucid, same pdfedit and kernel versions as original reporter. Marking as confirmed.

Changed in pdfedit (Ubuntu):
status: New → Confirmed

StacktraceTop:mcheck_pedantic (func=<value optimized out>)
?? ()
?? ()
~_Rb_tree_impl (this=0x4e004500430049)
XRef::destroyInternals (this=0x2277f90)

Changed in pdfedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
dino99 (9d9) wrote :

This version is outdated and no more supported

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

Other bug subscribers