Re: is this a memory leak?

It saves a copy from that pointer in the aclCheck_t structure, when the
aclChecklistCreate is called.

When aclChecklistFree is called that memory is freed.

In the other word there are two copies from that pointer. It uses
the second one to free it.

On Wed, 13 Dec 2000, Robert Collins wrote:

> In client_side.c, clientAccessCheckDone,
>
> ==
> debug(33, 2) ("The request %s %s is %s, because it matched '%s'\n",
> RequestMethodStr[http->request->method], http->uri,
> answer == ACCESS_ALLOWED ? "ALLOWED" : "DENIED",
> AclMatchedName ? AclMatchedName : "NO ACL's");
> if (http->acl_checklist->auth_user)
> proxy_auth_msg = http->acl_checklist->auth_user->message;
> http->acl_checklist = NULL;
> if (answer == ACCESS_ALLOWED) {
> safe_free(http->uri);
> http->uri = xstrdup(urlCanonical(http->request));
> assert(http->redirect_state == REDIRECT_NONE);
> ==
>
> the http->acl_checklist = NULL line concerns me: where does the checklist get freed?
>
> Rob
>
Received on Tue Dec 19 2000 - 07:09:44 MST