Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 559625

Summary: Segfault if FailoverManager is closed before being opened.
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Gordon Sim <gsim>
Status: CLOSED ERRATA QA Contact: Frantisek Reznicek <freznice>
Severity: medium Docs Contact:
Priority: high    
Version: 1.2CC: esammons, freznice
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
If a 'FailoverManager' instance was closed before it was opened, it caused a segmentation fault. With this update, the segmentation no longer occurs in the aforementioned case.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:07:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The reproducer + backtrace none

Description Gordon Sim 2010-01-28 16:02:10 UTC 
Description of problem:

If a FailoverManager instance is closed before it has been opened it will cause a seg fault.

Version-Release number of selected component (if applicable):

1.2

How reproducible:

Readily.

Steps to Reproduce:
1. Instantiate a FailoverManager instance
2. call close on it
3.
  
Actual results:

Seg fault

Expected results:

No seg fault
Additional info:
Comment 1 Frantisek Reznicek 2010-01-29 08:53:13 UTC 
Created attachment 387527 [details]
The reproducer + backtrace

The original reproducer including instructions how to compile including  backtrace which was seen on RHEL5.4 x86_64 and F8 x86_64.
Comment 2 Gordon Sim 2010-01-29 10:41:30 UTC 
Already fixed on trunk as r825869; will be part of 1.3 package.
Comment 4 Frantisek Reznicek 2010-10-04 12:37:40 UTC 
The issue has been fixed, tested on RHEL 4.8 / 5.5 i386 / x86_64 on packages:

python-qmf-0.7.946106-13.el5
python-qpid-0.7.946106-14.el5
qmf-0.7.946106-17.el5
qmf-devel-0.7.946106-17.el5
qpid-cpp-client-0.7.946106-17.el5
qpid-cpp-client-devel-0.7.946106-17.el5
qpid-cpp-client-devel-docs-0.7.946106-17.el5
qpid-cpp-client-rdma-0.7.946106-17.el5
qpid-cpp-client-ssl-0.7.946106-17.el5
qpid-cpp-mrg-debuginfo-0.7.946106-17.el5
qpid-cpp-server-0.7.946106-17.el5
qpid-cpp-server-cluster-0.7.946106-17.el5
qpid-cpp-server-devel-0.7.946106-17.el5
qpid-cpp-server-rdma-0.7.946106-17.el5
qpid-cpp-server-ssl-0.7.946106-17.el5
qpid-cpp-server-store-0.7.946106-17.el5
qpid-cpp-server-xml-0.7.946106-17.el5
qpid-dotnet-0.4.738274-2.el5
qpid-java-client-0.7.946106-10.el5
qpid-java-common-0.7.946106-10.el5
qpid-tools-0.7.946106-11.el5
ruby-qmf-0.7.946106-17.el5
ruby-qpid-0.7.946106-2.el5

-> VERIFIED
Comment 5 Martin Prpič 2010-10-10 10:08:12 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
If a 'FailoverManager' instance was closed before it was opened, it caused a segmentation fault. With this update, the segmentation no longer occurs in the aforementioned case.
Comment 7 errata-xmlrpc 2010-10-14 16:07:20 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html