| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
It's annoying when you use
p talloc_report_full(ctx, fopen("/tmp/xx","w"))
in gdb, and if you don't have write permission on the file then
you get a segv.
|
| |
|
|
|
|
|
| |
If NULL tracking is enabled after the autofree context is initialised
then autofree ends up separate from the null_context. This means that
talloc_report_full() doesn't report the autofree context. Fix this by
reparenting the autofree context when we create the null_context.
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
|
|
| |
parentheses
Michael
|
| |
|
|
|
|
| |
by first concatenating multilint parentheses and removing typefes afterwards.
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
|
|
|
|
| |
When we get a double free abort from talloc it is often hard to work
out where the first free came from. This patch takes advantage of the
fact that _talloc_free() now takes a location the free was called from
to allow the double free abort code to print the location of the first
free that conflicts.
|
| | |
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
| |
Michael
|
| |
|
|
|
|
| |
Simply run "make abi_checks" to call the abi check script appropriately.
Michael
|
| |
|
|
|
|
|
|
|
| |
USAGE: abi_checks.sh LIBRARY_NAME header1 [header2 ...]
This creates symbol signature lists using the mksyms and mksigs scripts
and compares them with the checked in lists.
Michael
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This produces output like the output gcc produces when
invoked with the -aux-info switch.
Run like this: cat talloc.h | ./script/mksigs.pl
This simple parser is probably too coarse to handle all possible
header files, but it does treat talloc.h correctly.
Michael
|
| |
|
|
| |
Michael
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
metze
|
| |
|
|
| |
metze
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
metze
|
| |
|
|
| |
metze
|
| |
|
|
| |
metze
|
| |
|
|
|
|
|
| |
So that the application can setup a log function to get ERROR
and WARNING messages.
metze
|
| |
|
|
|
|
| |
We have to many callers, which rely on that talloc_steal() never fails.
metze
|
| |
|
|
| |
metze
|
| |
|
|
| |
metze
|
| |
|
|
| |
metze
|
| |
|
|
|
|
|
|
|
| |
not exit
This will be useful in the testsuite,
where we could check if an abort would happen.
metze
|
| |
|
|
| |
metze
|
| |
|
|
|
|
| |
null_context
metze
|
| |
|
|
|
| |
Use py_talloc_reference in DCE/RPC code, fixes
access to SAMR pipe.
|
| | |
|
| | |
|
| |
|
|
| |
metze
|
| |
|
|
|
|
|
| |
This is needed to prevent samba3 and samba4 from using an ABI
incompatible system version of talloc
See ongoing discussion on the samba-technical mailing list
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The previous code caused memory leaks, and also caused situations
where talloc_free could be called on pointers with multiple parents
The new approach is to have two functions:
py_talloc_import : steals the pointer, so it becomes wholly owned by
the python object
py_talloc_reference: uses a reference, so it is owned by both python
and C
|
| |
|
|
|
| |
This makes sure we do not include foreign object files or other
build byproducts by mistake.
|
| |
|
|
|
|
|
|
| |
This is a first attempt at exporting symbols only for public functions
We also provide a rudimentary ABI checker that tries to check that
function signatures are not changed by mistake.
Given our use of macros this is not an API checker.
It's all based on talloc.h contents and the gcc -aux-info option
|