Re: Finding memory bugs automatically

To: Roland Illig <roland.illig%gmx.de@localhost>
Subject: Re: Finding memory bugs automatically
From: Martin Husemann <martin%duskware.de@localhost>
Date: Sun, 2 Oct 2022 09:33:56 +0200

On Sun, Oct 02, 2022 at 12:28:41AM +0200, Roland Illig wrote:
> Hi,
> 
> Do any of the releng builds and tests run with MALLOC_CONF=junk:true?

No.

> If not, why isn't there such a mode, and is there an alternative memory
> allocator that can find these kinds of bugs?

Using COPTS -fsanitize=address is a good way to find memory bugs, but
it turns off ASLR, only works on a few architectures and causes a quite heavy
performance impact.

Martin

References:
- Finding memory bugs automatically
  - From: Roland Illig

Prev by Date: daily CVS update output
Next by Date: NetBSD Security Advisory 2022-002: Coredump credential reference count leak
Previous by Thread: Finding memory bugs automatically
Next by Thread: NetBSD Security Advisory 2022-002: Coredump credential reference count leak
Indexes:

Home | Main Index | Thread Index | Old Index