[Insight-developers] A couple patches for the release branch

[Bradley Lowekamp]

Matt,

Thanks!

Things are looking looking pretty good on the dashboard. And I am just wrapping a couple maintenance issue up so thing are well under control.

When there RC is announced there will be some binary downloads available. Help will be needed to check these out to make sure they are good to go on all the platforms.

Thanks!
Brad

On Sep 10, 2013, at 12:33 PM, Matt McCormick <matt.mccormick at kitware.com> wrote:

> Hi Brad,
> 
> SimpleITK 0.7 RC will be excellent!  Let me know what I can do to help.
> 
> I have push those two patches on the release branch.
> 
> Thanks,
> Matt
> 
> On Tue, Sep 10, 2013 at 12:24 PM, Bradley Lowekamp
> <blowekamp at mail.nih.gov> wrote:
>> Hello Matt,
>> 
>> I am trying to get a RC for SimpleITK 0.7 done ASAP. I ran into a couple bug in ITK causing segfault and valgrind defects.
>> 
>> Please merge the following commits into release:
>> 
>> $ git log release..53bcb4c
>> commit 53bcb4cb05952358a6e579afdb52ebc044762f56
>> Author: Bradley Lowekamp <blowekamp at mail.nih.gov>
>> Date:   Mon Sep 9 14:35:38 2013 -0400
>> 
>>    BUG: Fix uninitialized m_Spacing in SignedMaurerDistance
>> 
>>    If PrintSelf was called before execution not value had been assigned
>>    to the m_Spacing variable. This defect was detected by Valgrind on the
>>    SimpleITK dashboard.
>> 
>>    Change-Id: I206f9c6fb4fb4d524922e3fcf973051f3f165769
>> 
>> $ git log release..113a1b0
>> commit 113a1b071fb3eb9608c047aaab32176e98960eab
>> Author: Bradley Lowekamp <blowekamp at mail.nih.gov>
>> Date:   Sun Sep 8 14:10:38 2013 -0400
>> 
>>    BUG: Don't print null bias field
>> 
>>    Printing the N4BiasFieldCorrection before execution was causing a
>>    segfault. Print "(null)" when null IVAR is encountered.
>> 
>>    Change-Id: I1af252f0734ecd6d524cdd2eb7731a77d096b9cc
>> 
>> 
>> Thanks,
>> Brad