This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] posix: Remove dynamic memory allocation from execl{e,p}
- From: Zack Weinberg <zackw at panix dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 29 Jan 2016 10:00:36 -0500
- Subject: Re: [PATCH] posix: Remove dynamic memory allocation from execl{e,p}
- Authentication-results: sourceware.org; auth=none
- References: <1454075599-2304-1-git-send-email-adhemerval dot zanella at linaro dot org>
On Fri, Jan 29, 2016 at 8:53 AM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> GLIBC execl{e,p} implementation might use malloc if the total number of
> arguments exceeds initial assumption size (1024). This might lead to
> issues in two situations: [...]
I think it would help the discussion if you could outline the
conditions under which these functions need to allocate memory in the
first place. Does it happen all the time, or only when falling back
to non-#! shell script invocation, or what?
zw