On Wed, Jun 21, 2023 at 3:09 PM Chet Ramey wrote:
> Have you considered running `make tests' on a bash binary built with this
> configuration? I'd be interested in those results.
I have, but unfortunately this generates quite a few reports that are
a little tricky to chase down. The main difficu
On 6/21/23 1:36 PM, Grisha Levit wrote:
I actually couldn't figure out how to get useful results from
LeakSanitizer on macOS. It's disabled in Apple's build of clang and
though it's enabled in homebrew's it seemed to be producing bogus
results with unusable traces.
So I was testing on Linux, c
On Wed, Jun 21, 2023, 10:08 Chet Ramey wrote:
>
> On 6/17/23 4:02 AM, Grisha Levit wrote:
> > Found mostly by normal usage running a no-bash-malloc build with clang's
> > LeakSanitizer enabled.
>
> Are you running this on macOS or some other system?
I actually couldn't figure out how to get usefu
On 6/17/23 4:02 AM, Grisha Levit wrote:
Found mostly by normal usage running a no-bash-malloc build with clang's
LeakSanitizer enabled.
Are you running this on macOS or some other system?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'
Found mostly by normal usage running a no-bash-malloc build with clang's
LeakSanitizer enabled. So far seems to provide very accurate results with
little overhead.
* arrayfunc.c
- quote_compound_array_word: make sure to free VALUE
- bind_assoc_var_internal: if assigning to a dynamic variable, make
