mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
91c1053413
Signed-off-by: Jelmer Vernooij <jelmer@samba.org> Reviewed-By: Andrew Bartlett <abartlet@samba.org> Autobuild-User(master): Jelmer Vernooij <jelmer@samba.org> Autobuild-Date(master): Thu Nov 28 02:24:45 CET 2013 on sn-devel-104
154 lines
6.3 KiB
Plaintext
154 lines
6.3 KiB
Plaintext
Using talloc in Samba4
|
|
======================
|
|
|
|
.. contents::
|
|
|
|
Jelmer Vernooij
|
|
August 2013
|
|
|
|
The most current version of this document is available at
|
|
http://samba.org/ftp/unpacked/talloc/pytalloc_guide.txt
|
|
|
|
pytalloc is a small library that provides glue for wrapping
|
|
talloc-allocated objects from C in Python objects.
|
|
|
|
What is pytalloc, and what is it not?
|
|
-------------------------------------
|
|
|
|
pytalloc is merely a helper library - it provides a convenient base type object
|
|
for objects that wrap talloc-maintained memory in C. It won't write your
|
|
bindings for you but it will make it easier to write C bindings that involve
|
|
talloc, and take away some of the boiler plate.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
pytalloc_Object
|
|
|
|
This is the new base class that all Python objects that wrap talloc pointers
|
|
derive from. It is itself a subclass of the "Object" type that all objects
|
|
in Python derive from.
|
|
|
|
Note that you will almost never create objects of the pytalloc_Object type
|
|
itself, as they are just opaque pointers that can not be accessed from
|
|
Python. A common pattern is other objects that subclass pytalloc_Object and
|
|
rely on it for their memory management.
|
|
|
|
Each `pytalloc_Object` wraps two core of information - a talloc context
|
|
and a pointer. The pointer is the actual data that is wrapped. The talloc
|
|
context is used for memory management purposes only; when the wrapping Python object
|
|
goes away, it unlinks the talloc context. The talloc context pointer and the ptr
|
|
can (and often do) have the same value.
|
|
|
|
Each pytalloc_Object has a custom __repr__ implementation that
|
|
describes that it is a talloc object and the location of the
|
|
pointer it is wrapping. it also has a custom __cmp__/__eq__/__neq__ method that
|
|
compares the pointers the object is wrapping rather than the objects
|
|
themselves (since there can be multiple objects that wrap the same talloc
|
|
pointer).
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyTypeObject *pytalloc_GetObjectType(void)
|
|
|
|
Obtain a reference to the PyTypeObject for `pytalloc_Object`. The reference
|
|
counter for the object will be incremented, so the caller will have to
|
|
decrement it when it no longer needs it (using `Py_DECREF`).
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-
|
|
int pytalloc_Check(PyObject *)
|
|
|
|
Check whether a specific object is a talloc Object. Returns non-zero if it is
|
|
a pytalloc_Object and zero otherwise.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
type *pytalloc_get_type(PyObject *py_obj, type)
|
|
|
|
Retrieve the pointer from a `pytalloc_Object` py_obj. type should be a
|
|
C type, similar to a type passed to `talloc_get_type`.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
pytalloc_get_ptr(PyObject *py_obj)
|
|
|
|
Retrieve the pointer from a `pytalloc_Object` py_obj. There is no
|
|
type checking - use `pytalloc_get_type` if possible.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
TALLOC_CTX *pytalloc_get_mem_ctx(PyObject *py_obj)
|
|
|
|
Retrieve the talloc context associated with a pytalloc_Object.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_steal_ex(PyTypeObject *py_type, TALLOC_CTX *mem_ctx, void *ptr)
|
|
|
|
Create a new Python wrapping object for a talloc pointer and context, with
|
|
py_type as associated Python sub type object.
|
|
|
|
This will *not* increment the reference counter for the talloc context,
|
|
so the caller should make sure such an increment has happened. When the Python
|
|
object goes away, it will unreference the talloc context.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_steal(PyTypeObject *py_type, void *ptr)
|
|
|
|
Create a new Python wrapping object for a talloc pointer and context, with
|
|
py_type as associated Python sub type object.
|
|
|
|
This will *not* increment the reference counter for the talloc context,
|
|
so the caller should make sure such an increment has happened. When the Python
|
|
object goes away, it will unreference the talloc context.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_reference_ex(PyTypeObject *py_type, TALLOC_CTX *mem_ctx, void *ptr)
|
|
|
|
Create a new Python wrapping object for a talloc pointer and context, with
|
|
py_type as associated Python sub type object.
|
|
|
|
This will increment the reference counter for the talloc context.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_reference(PyTypeObject *py_type, void *talloc_ptr)
|
|
|
|
Create a new Python wrapping object for a talloc pointer, with
|
|
py_type as associated Python sub type object. The pointer will also be used
|
|
as the talloc context.
|
|
|
|
This will increment the reference counter for the talloc context.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_new(type, PyTypeObject *typeobj)
|
|
|
|
Create a new, empty pytalloc_Object with the specified Python type object. type
|
|
should be a C type, similar to talloc_new().
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
PyObject *pytalloc_CObject_FromTallocPtr(void *);
|
|
|
|
Create a new pytalloc_Object for an abitrary talloc-maintained C pointer. This will
|
|
use a generic VoidPtr Python type, which just provides an opaque object in
|
|
Python. The caller is responsible for incrementing the talloc reference count before calling
|
|
this function - it will dereference the talloc pointer when it is garbage collected.
|
|
|
|
Debug function for talloc in Python
|
|
-----------------------------------
|
|
|
|
The "talloc" module in Python provides a couple of functions that can be used
|
|
to debug issues with objects wrapped by pytalloc.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
report_full(obj?)
|
|
|
|
Print a full report on a specific object or on all allocated objects by Python.
|
|
Same behaviour as the `talloc_report_full()` function that is provided by
|
|
C talloc.
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
enable_null_tracking()
|
|
|
|
This enables tracking of the NULL memory context without enabling leak
|
|
reporting on exit. Useful for when you want to do your own leak
|
|
reporting call via talloc_report_null_full().
|
|
|
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
|
pytalloc_total_blocks(obj?)
|
|
|
|
Return the talloc block count for all allocated objects or a specific object if
|
|
specified.
|