Hi Aida,
This kind of problems could be difficult to solve because of the
low reproducibility. It's easier to fix a bug when you can reproduce
it in your machine under specific steps and in Debug mode. However,
your problem arise only in release mode, in specific machines and
randomly (sometimes yes, and sometimes not). Could you provide more
details when you say "doesn't work correctly"?
The best recommendations I can give you are:
1. Isolate the problem by simplification:
1.1. Try to remove as much components as possible from GIMIAS
and keep only the components that allow you to reproduce the problem.
For example you can create a clinical workflow and select a very
reduced number of components, removing the toolbars, widgets, ... You
can also test your code in a separate application.
1.2. Simplify your code: If the code involved in the problem
affects 4 classes and 10 functions, then remove the blocks of code
that are not needed to reproduce the problem. This can help you to
focus on the pieces of code that are causing the problem.
1.3. Simplify the steps: Try to use the smallest image
possible and the smallest number of steps. For example if the problem
can be reproduced in 3 steps: load image, registration and
segmentation, try to reproduce it in 2 steps: load image,
segmentation. This will help you to isolate the problem and reproduce
it faster
1.4. Debug in release mode: For debugging in release mode you
can use std::cout. This could provide you more information about the
location of the piece of code that is causing the problem
2. Isolate the problem by changing the steps: try to test the
problem but changing specific steps. For example using another input
image, another computer, another parameters. Sometimes the problem
could be in the pixel type of the image, or a specific computer has a
specific configuration that causes the problem
3. Check your source code: Check that all variables are correctly
initialized. When a variable is not initialized, for example in the
constructor of a class, it will take different values in debug and
release mode. This could be the reason why the executable behavior is
different in each mode.
4. Specific tips: You can check that the machine where you can
reproduce the problem has the last Visual Studio redistributable
package version. You can find the last redistributable package of
Visual Studio 2008 for 32 bits here:
http://www.microsoft.com/en-us/download/details.aspx?id=5582
I hope some of these recommendations can help you to find the
cause of the problem.
Best regards,
Xavi
2012/8/1 Aida Ninyerola <[email protected]>:
> Hi,
>
> When I launch Gimias from my Release folder all works perfectly. If I paste
> this folder to another pc, I can run Gimias without any problem but my
> plugin doesn't work correctly. Some days ago I did the same and I had no
> problems.
>
> What can I check?
>
> Thanks,
> Aida
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Gimias-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/gimias-developers
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Gimias-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gimias-developers
