Andrew Tridgell c60ff99c31 r2674: I have realised that talloc() should have its context marked const, as ...

a const pointer really means that "the data pointed to by this pointer
won't change", and that is certainly true of talloc(). The fact that
some behind-the-scenes meta-data can change doesn't matter from the
point of view of const.

this fixes a number of const warnings caused by const data structures
being passed as talloc contexts. That will no longer generate a
warning.

also changed the talloc leak reporting option from --leak-check to
--leak-report, as all it does is generate a report on exit. A new
--leak-report-full option has been added that shows the complete tree
of memory allocations, which is is quite useful in tracking things down.

NOTE: I find it quite useful to insert talloc_report_full(ptr, stderr)
calls at strategic points in the code while debugging memory
allocation problems, particularly before freeing a major context (such
as the connection context). This allows you to see if that context has
been accumulating too much data, such as per-request data, which
should have been freed when the request finished.

2007-10-10 12:59:20 -05:00

..

config.m4

r665: merge over the new build system from my tmp branch

2007-10-10 12:53:36 -05:00

popt_common.c

r2674: I have realised that talloc() should have its context marked const, as

2007-10-10 12:59:20 -05:00

popt_common.h

r1972: cmdline_auth_info does not need to be declared global

2007-10-10 12:58:14 -05:00

readline.c

r2003: got rid of next_token_nr(), which involved some horrible globals

2007-10-10 12:58:16 -05:00