Hi all, Hi Sascha,
I did more tests and discovered that my tests stopped working when I
added "AUTOLOAD_WITH MitkCore" to my IO module. When I remove it, clean
and build again, ctest outputs normal messages like
1/N Test #1: BoneDensityTest999
.............................***Failed 0.34 sec
2/N Test #18: BoundingObjectTest1
............................***Exception: SegFault 6.33 sec
which can now be runned and debugged.
As I wrote in my first message, we added a "AUTOLOAD_WITH MitkCore" in
our IO module because I think it's mandatory for the Activator to
Register all the readers and writers. I simply copied what I saw in MITK
IOExt. What is the right way to do that? Should I use one of our own
module instead of "MitkCore"?
Le 2014-12-10 08:25, Nil Goyette a écrit :
Hi Sascha,
Thank you for your answer. Yes, I built our applications from a
"fresh" cmake Configure/Generate when I started. Just to be sure , I
deleted my build directory and built everything again. It didn't
change anything. I still have the same problems I described in my last
message.
Le 2014-12-09 14:06, Sascha Zelzer a écrit :
Hi Nil,
this looks like some strange build tree artifacts, so before further
investigations I need to ask if you did a clean build or re-used an
existing build tree during the migration.
Thanks,
Sascha
On 12/09/2014 07:12 PM, Nil Goyette wrote:
Hi all,
I ported our applications to MITK 2014.10 and several tests fail
since. I investigated and found some facts which will hopefully help
you help me :)
They do nothing if I start them individually with *TestDriver.exe.
They simpy print \n and return to the command line.
One time though, I was able to run one test, not sure what I did. It
printed:
3: 0.18 core.int.coreAct WARNING: In
`anonymous-namespace'::load_impl at
..\..\..\..\..\Core\CppMicroServices\core\src\util\usUtils.cpp:90 :
L'accès à cet emplacement de la mémoire n'est pas valide.(French
for: Access to this memory address is invalid)
3: 0.18 core.int.coreAct WARNING: In us::AutoLoadModulesFromPath at
..\..\..\..\..\Core\CppMicroServices\core\src\util\usUtils.cpp:176 :
Auto-loading of module
C:\Imeka\plitk\imeka-plitk\_VS12_x32_2014.10\bin\MitkCore\Release\ImekaIO.dll
failed.
Available tests:
0. VFFReaderTest
I understand the second message. We added a "AUTOLOAD_WITH MitkCore"
in our IO module because I think it's mandatory for the Activator to
Register all the readers and writers. Is there another way?
The error messages doesn't help me much:
18/N Test #18: BoundingObjectTest1
............................***Exception: Other 0.37 sec
19/N Test #19: VFFReaderTest1
.................................***Exception: Other 0.41 sec
... and it's not better with -VV
Running one of the failing test in debug (to understand what Other
Exception is) leads me to a strange place. The place itself
(dbgheap.c) is probably uninteresting to MITK, but the stack trace
might be of interest. Take a look at the attachment. We can see that
it never enters the test. It just kills itself before. This only
happens in debug though.
I'm unsure what to do next. I know the content of my test is ok (a
simple std::cout make them fail...) but I can't get them to run. I
would appreciate any help! Thanks and have a nice day.
--
Logo Imeka <http://imeka.ca/> Nil Goyette, M.Sc.
www.imeka.ca <http://imeka.ca/>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
