Bug 1042751

Summary: [abrt] avogadro-1.0.3-16.fc19: std::ostream::flush: Process /usr/bin/avogadro was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: pankaj pandey <pankaj86>
Component: avogadroAssignee: Kevin Kofler <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b83190d0114ab46135fa4d6c5c0dfbaab3323b65
Whiteboard: abrt_hash:985f6b4e5bd27203ecbc5c8688e06347b51e9fdb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:37:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description pankaj pandey 2013-12-13 09:31:04 UTC 
Description of problem:
Normally using avogadro, running some optimizations. Avogadro is very unstable.

Version-Release number of selected component:
avogadro-1.0.3-16.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        avogadro
crash_function: std::ostream::flush
executable:     /usr/bin/avogadro
kernel:         3.11.10-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 std::ostream::flush at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream.tcc:219
 #1 std::ostream::sentry::sentry at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream.tcc:52
 #2 std::__ostream_insert<char, std::char_traits<char> > at /usr/src/debug/gcc-4.8.2-20131017/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/ostream_insert.h:82
 #3 operator<< <std::char_traits<char> > at /usr/include/c++/4.8.1/ostream:535
 #4 OBFFLog at /usr/src/debug/openbabel-2.3.2/include/openbabel/forcefield.h:1013
 #5 OpenBabel::OBForceField::PrintTypes at /usr/src/debug/openbabel-2.3.2/src/forcefield.cpp:781
 #6 OpenBabel::OBForceField::Setup at /usr/src/debug/openbabel-2.3.2/src/forcefield.cpp:891
 #7 Avogadro::Molecule::dipoleMoment at /usr/src/debug/avogadro-1.0.3/libavogadro/src/molecule.cpp:727
 #8 Avogadro::DipoleEngine::updateDipole at /usr/src/debug/avogadro-1.0.3/libavogadro/src/engines/dipoleengine.cpp:158
 #9 Avogadro::DipoleEngine::renderOpaque at /usr/src/debug/avogadro-1.0.3/libavogadro/src/engines/dipoleengine.cpp:68
Comment 1 pankaj pandey 2013-12-13 09:31:15 UTC 
Created attachment 836246 [details]
File: backtrace
Comment 2 pankaj pandey 2013-12-13 09:31:17 UTC 
Created attachment 836247 [details]
File: cgroup
Comment 3 pankaj pandey 2013-12-13 09:31:20 UTC 
Created attachment 836248 [details]
File: core_backtrace
Comment 4 pankaj pandey 2013-12-13 09:31:33 UTC 
Created attachment 836249 [details]
File: dso_list
Comment 5 pankaj pandey 2013-12-13 09:31:35 UTC 
Created attachment 836250 [details]
File: environ
Comment 6 pankaj pandey 2013-12-13 09:31:37 UTC 
Created attachment 836251 [details]
File: exploitable
Comment 7 pankaj pandey 2013-12-13 09:31:40 UTC 
Created attachment 836252 [details]
File: limits
Comment 8 pankaj pandey 2013-12-13 09:31:46 UTC 
Created attachment 836253 [details]
File: maps
Comment 9 pankaj pandey 2013-12-13 09:31:48 UTC 
Created attachment 836254 [details]
File: open_fds
Comment 10 pankaj pandey 2013-12-13 09:31:50 UTC 
Created attachment 836255 [details]
File: proc_pid_status
Comment 11 pankaj pandey 2013-12-13 09:31:53 UTC 
Created attachment 836256 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-01-09 20:50:56 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2015-02-17 19:37:50 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.