testdisk crashed with SIGSEGV

Bug #1412263 reported by Marcos K
This bug report is a duplicate of:  Bug #1412262: testdisk crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
testdisk (Ubuntu)
New
Undecided
Unassigned

Bug Description

P : list file on ntfs partition

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: testdisk 6.14-2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 19 00:04:36 2015
ExecutablePath: /usr/bin/testdisk
InstallationDate: Installed on 2014-02-17 (335 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: testdisk
SegvAnalysis:
 Segfault happened at: 0x7f39eb6b2da6 <__strcmp_ssse3+22>: movlpd (%rdi),%xmm1
 PC (0x7f39eb6b2da6) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: testdisk
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: testdisk crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-05-23 (240 days ago)
UserGroups:

Revision history for this message
Marcos K (g-ubuntu-com-y) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

tags: removed: need-amd64-retrace
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.