4 Commits

Author	SHA1	Message	Date
Volker Lendecke	5274d8cda3	Only realloc the talloc stack if necessary ... (This used to be commit c7cb98d486)	2008-01-08 22:18:08 +01:00
Volker Lendecke	8d261ee580	talloc_stackframe only needs 1 talloc ... (This used to be commit c0c2084d40)	2008-01-07 21:18:00 +01:00
Volker Lendecke	2800362e3f	r24902: DEBUG might use talloc_tos() itself... ... (This used to be commit 1b39374a17)	2007-10-10 12:30:28 -05:00
Volker Lendecke	929e1d9920	r24809: Consolidate the use of temporary talloc contexts. ... This adds the two functions talloc_stackframe() and talloc_tos(). * When a new talloc stackframe is allocated with talloc_stackframe(), then * the TALLOC_CTX returned with talloc_tos() is reset to that new * frame. Whenever that stack frame is TALLOC_FREE()'ed, then the reverse * happens: The previous talloc_tos() is restored. * * This API is designed to be robust in the sense that if someone forgets to * TALLOC_FREE() a stackframe, then the next outer one correctly cleans up and * resets the talloc_tos(). The original motivation for this patch was to get rid of the sid_string_static & friends buffers. Explicitly passing talloc context everywhere clutters code too much for my taste, so an implicit talloc_tos() is introduced here. Many of these static buffers are replaced by a single static pointer. The intended use would thus be that low-level functions can rather freely push stuff to talloc_tos, the upper layers clean up by freeing the stackframe. The more of these stackframes are used and correctly freed the more exact the memory cleanup happens. This patch removes the main_loop_talloc_ctx, tmp_talloc_ctx and lp_talloc_ctx (did I forget any?) So, never do a tmp_ctx = talloc_init("foo"); anymore, instead, use tmp_ctx = talloc_stackframe() :-) Volker (This used to be commit 6585ea2cb7)	2007-10-10 12:30:24 -05:00