Bug 684449 - [abrt] hugin-2010.2.0-1.fc14: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV)
Summary: [abrt] hugin-2010.2.0-1.fc14: Process /usr/bin/hugin was killed by signal 11 ...
Keywords:
Status: CLOSED DUPLICATE of bug 650696
Alias: None
Product: Fedora
Classification: Fedora
Component: hugin
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Postle
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0d0b76a189fa69b69321d6ea807...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-12 17:26 UTC by gregor
Modified: 2012-03-21 16:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:38:55 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (202.34 KB, text/plain)
2011-03-12 17:27 UTC, gregor
no flags Details

Description gregor 2011-03-12 17:26:58 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 207199 bytes
cmdline: hugin
component: hugin
Attached file: coredump, 332271616 bytes
crash_function: vigra::inspectLine<vigra::RGBValue<unsigned char, 0u, 1u, 2u>*, vigra::RGBToGrayAccessor<vigra::RGBValue<unsigned char, 0u, 1u, 2u> >, vigra::FindAverage<unsigned char> >(vigra::RGBValue<unsigned char, 0u, 1u, 2u>*, vigra::RGBValue<unsigned char, 0u, 1u, 2u>*, vigra::RGBToGrayAccessor<vigra::RGBValue<unsigned char, 0u, 1u, 2u> >, vigra::FindAverage<unsigned char>&)
executable: /usr/bin/hugin
kernel: 2.6.35.11-83.fc14.x86_64
package: hugin-2010.2.0-1.fc14
rating: 4
reason: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: crashed during autosearching controllopints (point 2 with the assitant)
time: 1299950719
uid: 500

Comment 1 gregor 2011-03-12 17:27:03 UTC
Created attachment 483919 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 16:38:55 UTC
Backtrace analysis found this bug to be similar to bug #650696, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 650696 ***


Note You need to log in before you can comment on or make changes to this bug.