[omniORB] omniORBpy memory leak using PyErr_SetObject

[Luke Deller]

Hello,

There are a few places in omniORBpy-3.2 which leak python exception objects.

The code seems to assume that the Python API function
PyErr_SetObject(PyObject *type, PyObject *value)
will steal a reference to "value", but it does not.

Attached is a patch to resolve this problem.

Regards,
Luke.
**********************************************************************************************
Important Note
This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this email are not necessarily the views of IRESS Market Technology Limited.

It is the duty of the recipient to virus scan and otherwise test the information provided before loading onto any computer system.
IRESS Market Technology Limited does not warrant that the information is free of a virus or any other defect or error.
**********************************************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: omniORBpy-3.2-except-memleak.patch
Type: application/octet-stream
Size: 2120 bytes
Desc: omniORBpy-3.2-except-memleak.patch
Url : http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20080403/939d5c51/omniORBpy-3.2-except-memleak.obj

[Duncan Grisby]

Post by Luke Deller
There are a few places in omniORBpy-3.2 which leak python exception objects.
The code seems to assume that the Python API function
PyErr_SetObject(PyObject *type, PyObject *value)
will steal a reference to "value", but it does not.

Thanks. I applied your patch the other day, but forgot to email you to
say I'd done it.

Cheers,

Duncan.