Age | Commit message (Collapse) | Author | Files | Lines |
|
pointers
(talloc.c)
...
> static inline int _talloc_free_internal(void *ptr, const char *location)
> {
> struct talloc_chunk *tc;
>
> if (unlikely(ptr == NULL)) {
> return -1;
> }
>
> tc = talloc_chunk_from_ptr(ptr);
...
Obviously this never had been documented before.
|
|
|
|
|
|
Thanks to the suggestion from simo
|
|
Signed-off-by: Stefan Metzmacher <metze@samba.org>
|
|
teach the abi check scripts to skip the DOXYGEN sections
fix the header to use #ifdef DOXYGEN and not #if DOXYGEN
|
|
|
|
Signed-off-by: Andrew Tridgell <tridge@samba.org>
|
|
Signed-off-by: Andrew Tridgell <tridge@samba.org>
|
|
When we disable null tracking, we need to move any existing objects
that are under the null_context to be parented by the true NULL
context.
We also need a new talloc_enable_null_tracking_no_autofree() function,
as the talloc testsuite cannot cope with the moving of the autofree
context under the null_context as it wants to check exact counts of
objects under the null_context, and smbtorture has a large number of
objects in the autofree_context from .init functions
|
|
We also use the major and minor versions in the TALLOC_MAGIC,
so that we can detect if two conflicting versions of talloc
are loaded in one process. In this case we use talloc_log() to
output a very useful debug message before we call
talloc_abort().
metze
|
|
metze
|
|
So that the application can setup a log function to get ERROR
and WARNING messages.
metze
|
|
|
|
These changes follow from the discussions on samba-technical. The
changes are in several parts, and stem from the inherent ambiguity
that was in talloc_free() and talloc_steal() when the pointer that is
being changes has more than one parent, via references.
The changes are:
1) when you call talloc_free() on a pointer with more than one parent
the free will fail, and talloc will log an error to stderr like this:
ERROR: talloc_free with references at some/foo.c:123
reference at other/bar.c:201
reference at other/foobar.c:641
2) Similarly, when you call talloc_steal() on a pointer with more
than one parent, the steal will fail and talloc will log an error to
stderr like this:
ERROR: talloc_steal with references at some/foo.c:123
reference at other/bar.c:201
3) A new function talloc_reparent() has been added to change a parent
in a controlled fashion. You need to supply both the old parent and
the new parent. It handles the case whether either the old parent was
a normal parent or a reference
The use of stderr in the logging is ugly (and potentially dangerous),
and will be removed in a future patch. We'll need to add a debug
registration function to talloc.
|
|
metze
|
|
|
|
comments"
This reverts commit d21212c9192b41a3fdc7e96cb9bf0125a1dc6c2d.
|
|
This reverts commit ba42320c7e9f5ccbd32eccbfb1f2d77e13b3a318.
|
|
This reverts commit cfce2d3611f225244fadf3d27d76371827fd6422.
|
|
This reverts commit db447d0c476699dbf7fa0567c67f5938674ec811.
|
|
This reverts commit 27944ed7452207ef3c686ff6bcd9c4e1cb7f36d8.
|
|
This reverts commit 02662d56c64f367bffa2febba9a396c15454cfdb.
|
|
This reverts commit 2ce70d4f5a30973b4cc083dbbb38b519007a31bd.
|
|
This reverts commit 3f81649b8dcadb3bd424f41d803dbd59f770b9ba.
|
|
This reverts commit 986c2e01cca0be993f1e52d3a27819f4044bfe4b.
|
|
This reverts commit 59dff5745528a3efe585cdeb03e2bedd6b2e404a.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
talloc_guide.txt was partly outdated, and as going through talloc.h now shows
it was incomplete.
|
|
metze
|
|
metze
|
|
metze
|
|
metze
|
|
|