On Wed, Oct 24, 2018 at 2:57 PM Rob Herring wrote:
>
> On Mon, Oct 22, 2018 at 4:25 PM Alan Tull wrote:
> >
> > On Thu, Oct 18, 2018 at 5:48 PM wrote:
> > >
> > > From: Frank Rowand
> > >
> > > Add checks to (1) overlay apply process and (2) memory freeing
> > > triggered by overlay release.
On Mon, Oct 22, 2018 at 4:25 PM Alan Tull wrote:
>
> On Thu, Oct 18, 2018 at 5:48 PM wrote:
> >
> > From: Frank Rowand
> >
> > Add checks to (1) overlay apply process and (2) memory freeing
> > triggered by overlay release. The checks are intended to detect
> > possible memory leaks and
On Thu, Oct 18, 2018 at 5:48 PM wrote:
>
> From: Frank Rowand
>
> Add checks to (1) overlay apply process and (2) memory freeing
> triggered by overlay release. The checks are intended to detect
> possible memory leaks and invalid overlays.
I've tested v5, nothing new to report.
Alan
>
> The
On 10/18/18 15:46, frowand.l...@gmail.com wrote:
> From: Frank Rowand
>
> Add checks to (1) overlay apply process and (2) memory freeing
> triggered by overlay release. The checks are intended to detect
> possible memory leaks and invalid overlays.
>
> The checks revealed bugs in existing
From: Frank Rowand
Add checks to (1) overlay apply process and (2) memory freeing
triggered by overlay release. The checks are intended to detect
possible memory leaks and invalid overlays.
The checks revealed bugs in existing code. Fixed the bugs.
While fixing bugs, noted other issues,
