testdisk crashed with SIGSEGV in malloc()

[Jānis Kangarooo]

Binary package hint: testdisk

I was using Testdisk and somewhere choosing i think P:list files for ntfs it crashed and showed terminal strange (still with photorec terminal gui but in the bottom line as just terminal with up and down giving previous terminal commands to choose)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: testdisk 6.11-1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jun 8 21:59:18 2010
ExecutablePath: /usr/sbin/testdisk
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: testdisk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x47483e: cmp 0xc(%edx),%edi
 PC (0x0047483e) ok
 source "0xc(%edx)" (0x0002000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: testdisk
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ext2fs_open2 () from /lib/libext2fs.so.2
 ext2fs_open () from /lib/libext2fs.so.2
Title: testdisk crashed with SIGSEGV in malloc()
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ext2fs_open2 () from /lib/libext2fs.so.2
 ext2fs_open () from /lib/libext2fs.so.2

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!