Public bug reported:
Binary package hint: shotwell
THIS IS THE SAME BUG AS 676949 BUT WITH DEBUGGING SYMBOLS
The interesting thing is, that it crashes with SIGSEGV in operator()++
this is really strange in my opinion.. Maybe they increment the contents
of a variable which is referenced by a bad pointer? b.t.w. its not a
problem in gexiv2 (676949) but in exiv2
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: shotwell 0.7.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.37-5.14-generic 2.6.37-rc2
Uname: Linux 2.6.37-5-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
CheckboxSubmission: f27e0f64e4c4a50e8fcdb1738914010b
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Sat Nov 20 17:15:13 2010
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: shotwell
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ffa332f9890
<gexiv2_metadata_get_orientation(GExiv2Metadata*)+144>: mov (%rax),%rax
PC (0x7ffa332f9890) ok
source "(%rax)" (0x6c8948f0245c8948) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
operator++ (self=0x1a12b60) at /usr/include/c++/4.5/bits/stl_list.h:223
__distance<std::_List_const_iterator<Exiv2::Exifdatum> > (self=0x1a12b60) at
/usr/include/c++/4.5/bits/stl_iterator_base_funcs.h:80
distance<std::_List_const_iterator<Exiv2::Exifdatum> > (self=0x1a12b60) at
/usr/include/c++/4.5/bits/stl_iterator_base_funcs.h:115
size (self=0x1a12b60) at /usr/include/c++/4.5/bits/stl_list.h:806
count (self=0x1a12b60) at /usr/include/exiv2/exif.hpp:520
Title: shotwell crashed with SIGSEGV in operator++()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
** Affects: shotwell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash natty
--
shotwell crashed with SIGSEGV in operator++()
https://bugs.launchpad.net/bugs/677871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
