[Insight-users] Image offset is giving bad pointer for large datasets (7Gb)

Arunachalam Kana Kana.Arunachalam at fh-wels.at
Fri Jul 10 08:49:32 EDT 2009


Hi Luis,

Thank you for your response. I ran the test program and the given the
results are given below along with detailed System information and what
option i used to compile itk.

System Information
------------------
Time of this report: 7/8/2009, 17:16:29
       Machine name: CT-DELL
   Operating System: Windows XP Professional x64 Edition (5.2, Build
3790) Service Pack 2 (3790.srv03_sp2_gdr.090319-1204)
           Language: English (Regional Setting: German) System
Manufacturer: Dell Inc.
       System Model: Precision WorkStation T7400  
               BIOS: Default System BIOS
          Processor: Intel(R) Pentium(R) III Xeon-Prozessor (8 CPUs),
~3.2GHz
             Memory: 65534MB RAM
          Page File: 717MB used, 65267MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters:
Not found
     DxDiag Version: 5.03.3790.3959 32bit Unicode


Itk compilation
---------------------
I have some doubts in this section.

CMake version: CMake 2.6-patch 4.

I selected the option Visual Studio 9 2008 Win64 before pressing the
configure button.

The current generator: Visual Studio 9 2008 Win64 (left bottom in
attached image itk_cmake.png)

But when i selected the advance view:

Build Name: Win32-vs9 (top of the image itk_cmake.png) To clear this, i
opened the cmakecache.txt (attached to this email) and it is written
"Build Name = Win32-vs9".

I thought when i use Visual Studio 9 2008 Win64 option the build name
would be Win64-vs9. I would like to clear this doubt. 
So, my Question is :
Is it correct to have Win32-vs9 in "Build Name" even after selecting
Visual Studio 9 2008 Win64 as "Current Generator"?

Microsoft visual studio 2008
---------------------
Configuration manager details: 
Active Solution Configuration: Debug
Active Solution Platform: x64

Test run details:
1. Program:
    unsigned long tt;
    std::cout << "size = " << sizeof(tt) << std::endl;
    tt  =  -1;
    std::cout << "tt = " << tt << std::endl; 
    output: size = 4; tt = 4294967295

2. Program:
    unsigned long long tt;
    std::cout << "size = " << sizeof(tt) << std::endl;
    tt  =  -1;
    std::cout << "tt = " << tt << std::endl; 
    output: size = 8; tt = 18446744073709551615 

I changed the configuration details:
--------------------------------------
Active Solution Configuration: Debug
Active Solution Platform: Win32

Test run details:
1. Program:
    unsigned long tt;
    std::cout << "size = " << sizeof(tt) << std::endl;
    tt  =  -1;
    std::cout << "tt = " << tt << std::endl; 
    output: size = 4; tt = 4294967295

2. Program:
    unsigned long long tt;
    std::cout << "size = " << sizeof(tt) << std::endl;
    tt  =  -1;
    std::cout << "tt = " << tt << std::endl; 
    output: size = 8; tt = 18446744073709551615 

For both Win32 and x64 i get the same result.
Unsigned long is 4 byte and unsigned long long is 8 byte.

I was a little confused after the result, so i searched for data type
ranges in msdn. Link below:

http://msdn.microsoft.com/en-us/library/s3f49ktz.aspx



More information about the Insight-users mailing list