Bug 624118 - C++ Messaging Client .NET binding fails to clone managed objects correctly
C++ Messaging Client .NET binding fails to clone managed objects correctly
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-sdk (Show other bugs)
All Linux
high Severity medium
: 1.3
: ---
Assigned To: Chuck Rolke
Frantisek Reznicek
Depends On:
  Show dependency treegraph
Reported: 2010-08-13 13:59 EDT by Chuck Rolke
Modified: 2015-11-15 20:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-12-11 15:25:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA QPID-2798 None None None Never

  None (edit)
Description Chuck Rolke 2010-08-13 13:59:48 EDT
Description of problem:

After cloning a managed object and then handling an exception, the process received an Access Violation while freeing the object and its clone.

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


How reproducible:

static, easy.

Steps to Reproduce:

The specific case that failed was
  request = receiver.fetch();
  address = request.ReplyTo;
  sender = session.CreateSender(address);

The bug occurs during the cloning of the Address object from the request.ReplyTo. After that line of code there are two managed objects that have pointers to the same unmanaged object. When the CreateSender function exits then the process will get an accvio during shutdown.

Additional info:


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