[Vm-dev] [Pharo-users] macOS VM builds with AddressSanitizer/LeakSanitizer

[Alistair Grant]

On Tue, 29 Jan 2019 at 15:32, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>
>
> ...
>
> So this is great.  The final step is seeing which FFI method invokes moz2d_draw_target_create_for_data_type and then the storage leak can be fixed.
> What would be wonderful is to capture your experience in diagnosing this storage leak as a guide to others.  But in what form?  One would be a blog post.  I’m nervous though because blogs sometimes disappear.  One would be some section in one of the READMEs in the source tree.  One would be a carefully written email to this list recapitulating or summarizing the experience.
>
> The advantage of the mailing list is that it won’t go away any time soon.  So how about writing a new message in this thread which summarizes?  It could be written as more of a guide “Storage leaks come in more than one variety...  To diagnose a leak in the C heap... To link against a C leak checker...” and include links to the other messages in this thread on the mail list serve for details “Specifics on how to modify the Mac build to link in the leak checker are ...”.
>
> What do you think?  What to others think?  How do we best capture this for posterity?

I would split this in two:

- The basic instructions on compiling with the leak checker should go
in the HowToBuild.
- The description you're suggesting above should go in
http://opensmalltalk.org/ as Ben suggested, or a wiki page in the
OpenSmalltalk-VM repository.

Each should provide a link to the other.

I'm not a big fan of github wiki pages, but they have two advantages:

- They keep the content with the code.
- They're relatively easy to download and back-up offline (in the
event that we decide to move the code elsewhere).

My preference would be http://opensmalltalk.org/, but I'm not sure
what the access rights on it are.  Actually, I didn't even know it
existed, thanks Ben!

As Tim said, email lists are hard to search, and can't be easily
updated.  Blog posts don't really lend themselves to being updated
either.

My 2c...

Cheers,
Alistair