Bug 559625 – Segfault if FailoverManager is closed before being opened.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 559625 - Segfault if FailoverManager is closed before being opened.

Summary:	Segfault if FailoverManager is closed before being opened.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	high Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Gordon Sim
QA Contact:	Frantisek Reznicek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-28 11:02 EST by Gordon Sim
Modified:	2015-11-15 20:11 EST (History)
CC List:	2 users (show)

See Also:
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 12:07:20 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
The reproducer + backtrace (12.41 KB, text/x-c++src) 2010-01-29 03:53 EST, Frantisek Reznicek	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Gordon Sim 2010-01-28 11:02:10 EST

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 03:53:13 EST

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 05:41:30 EST

Already fixed on trunk as r825869; will be part of 1.3 package.

Comment 4 Frantisek Reznicek 2010-10-04 08:37:40 EDT

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 06:08:12 EDT

    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 12:07:20 EDT

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

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