Re: Looking to contribute OMF support

[Ben Elliston <bje at au1 dot ibm dot com>]

> I won't make any promises about contributing zillions of patches but
> as long as you don't uncover rocket science bugs I may have written
> I'm sure you can gently bully me into fixing stuff when it
> breaks. :)

The problem is knowing when stuff has broken ..

> Are there any things specific to BFD that I can do to make my code
> more or less resilient to bit rot?  One thing I'm worried about that
> I thought was okay, is that I bfd_alloc gobs of memory everywhere
> without freeing them, relying instead on bfd_close to release the
> memory when objdump et al are done with the BFD.  But then I saw a
> recent message that seemed to say that that constituted a memory
> leak...

I think the best thing that you could do to ensure that your new code
doesn't break is to contribute test cases that can be used to catch
regressions.  The more tests, the merrier (within limits!)

Cheers, Ben