[Insight-developers] BillsBasement Nightly Failing Test
Luis Ibanez
luis.ibanez at kitware.com
Mon Feb 23 22:04:43 EST 2009
Hi Brad,
This error seems to be related to the changes in MetaImage.
Here is the backtrace that I get from GDB:
-----------------------------------------------------------------------
(gdb) run itkImageToCooccurrenceListAdaptorTest
/home/ibanez/src/Insight/Testing/Data/Input/HeadMRVolume.mhd
Starting program:
/home/ibanez/bin/InsightGcc4.3/Debug/bin/itkStatisticsTests
itkImageToCooccurrenceListAdaptorTest
/home/ibanez/src/Insight/Testing/Data/Input/HeadMRVolume.mhd
[Thread debugging using libthread_db enabled]
/usr/include/c++/4.3/debug/vector:237:error: attempt to subscript container
with out-of-bounds index 2, but container only holds 2 elements.
Objects involved in the operation:
sequence "this" @ 0x0xbf9e58fc {
type = NSt7__debug6vectorIlSaIlEEE;
}
[New Thread 0xb7d0e6c0 (LWP 8686)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7d0e6c0 (LWP 8686)]
0xb7fe4430 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7fe4430 in __kernel_vsyscall ()
#1 0xb7d3b8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7d3d268 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7ecd849 in __gnu_debug::_Error_formatter::_M_error () from
/usr/lib/libstdc++.so.6
#4 0x083c9d14 in std::__debug::vector<long, std::allocator<long>
>::operator[] (this=0xbf9e58fc, __n=2) at
/usr/include/c++/4.3/debug/vector:237
#5 0x083c9d53 in itk::ImageIORegion::SetIndex (this=0xbf9e58f4, i=2, idx=0)
at /home/ibanez/src/Insight/Code/IO/itkImageIORegion.h:183
#6 0x085a60b8 in itk::MetaImageIO::Read (this=0x9335f40, buffer=0x93501a8)
at /home/ibanez/src/Insight/Code/IO/itkMetaImageIO.cxx:840
#7 0x084a2efb in itk::ImageFileReader<itk::Image<float, 2u>,
itk::DefaultConvertPixelTraits<float> >::GenerateData (this=0x9331cf0) at
/home/ibanez/src/Insight/Code/IO/itkImageFileReader.txx:406
#8 0x0884cc49 in itk::ProcessObject::UpdateOutputData (this=0x9331cf0) at
/home/ibanez/src/Insight/Code/Common/itkProcessObject.cxx:991
#9 0x0883412b in itk::DataObject::UpdateOutputData (this=0x9334410) at
/home/ibanez/src/Insight/Code/Common/itkDataObject.cxx:420
#10 0x0883406a in itk::DataObject::Update (this=0x9334410) at
/home/ibanez/src/Insight/Code/Common/itkDataObject.cxx:344
#11 0x0884c00d in itk::ProcessObject::Update (this=0x9331cf0) at
/home/ibanez/src/Insight/Code/Common/itkProcessObject.cxx:619
#12 0x084855f3 in itkImageToCooccurrenceListAdaptorTest (argc=2,
argv=0xbf9e6008) at
/home/ibanez/src/Insight/Testing/Code/Numerics/Statistics/itkImageToCooccurrenceListAdaptorTest.cxx:53
#13 0x0838fe3d in main (ac=3, av=0xbf9e6004) at
/home/ibanez/src/Insight/Code/Common/itkTestMain.h:162
-----------------------------------------------------------------------
For some reason the itkImageIORegion thinks it is a 2D one
while the MetaImage is asking for the component [2].
Bill:
I'm looking at the CVS diff of the day that you pointed out.
Luis
-----------------------------------------------------------------------
On Mon, Feb 23, 2009 at 7:34 PM, Luis Ibanez <luis.ibanez at kitware.com>wrote:
> Hi Bill,
>
> I'm looking at it...
>
> building with gcc 4.3 and STL debug on...
>
> Luis
>
>
> ---------------------------
>
> Bill Lorensen wrote:
>
>> Luis,
>>
>> This build has stl debugging turned on. The test:
>> http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=277757
>> shows an issue. Typically the culprit can be found by running the test
>> from this build with gdb. However, I'm out of town and don't have
>> access to my basement machine.
>>
>> I notice that other platforms are crashing also. The failures started
>> on Jan 30. Since this test uses a meta file, I would look at the
>> changes to MetaImageIO that occurred that day:
>>
>> http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/IO/itkMetaImageIO.cxx?root=Insight&r1=1.89&r2=1.90
>>
>>
>> Bill
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20090223/3d03bbb4/attachment.htm>
More information about the Insight-developers
mailing list