c++ - Linker crash
- Ed (8/8) Apr 20 2007 Hi,
- Ed (8/16) Apr 20 2007 Found the trouble maker, it happens when you define a table > 1
- Walter Bright (3/12) Apr 20 2007 The easiest solution is to new() the array, rather than statically
- Ed (3/15) Apr 20 2007 How to "new()" is new to me, can you explain Walter?
- Walter Bright (2/21) Apr 20 2007
- Ed (6/23) Apr 21 2007 Ok, will find my way around. But, are you going to fix the linker
- Walter Bright (2/8) Apr 22 2007 It won't be fixed in the near future.
Hi, I am using the latest version but also previous versions produce the following error message: Unexpected OPTLINK termination at EIP=4000F982 The status line shows the module LIB/USER32.LIB The library is from 2 january 2006 and 70,144 Kb Any idea? Ed
Apr 20 2007
Found the trouble maker, it happens when you define a table > 1 million entries, for instance: #define EOC_MAX 1000000 static unsigned int hkw [EOC_MAX]; Now raise EOC_MAX to 2 million and the linker crashes. Hoping for a solution.... Ed == Quote from Ed (matador home.nl)'s articleHi, I am using the latest version but also previous versions produce the following error message: Unexpected OPTLINK termination at EIP=4000F982 The status line shows the module LIB/USER32.LIB The library is from 2 january 2006 and 70,144 Kb Any idea? Ed
Apr 20 2007
Ed wrote:Found the trouble maker, it happens when you define a table > 1 million entries, for instance: #define EOC_MAX 1000000 static unsigned int hkw [EOC_MAX]; Now raise EOC_MAX to 2 million and the linker crashes. Hoping for a solution....The easiest solution is to new() the array, rather than statically allocate it.
Apr 20 2007
How to "new()" is new to me, can you explain Walter? Ed == Quote from Walter Bright (newshound1 digitalmars.com)'s articleEd wrote:Found the trouble maker, it happens when you define a table > 1 million entries, for instance: #define EOC_MAX 1000000 static unsigned int hkw [EOC_MAX]; Now raise EOC_MAX to 2 million and the linker crashes. Hoping for a solution....The easiest solution is to new() the array, rather than statically allocate it.
Apr 20 2007
new() is C++. If you're using C, you can use malloc() instead. Ed wrote:How to "new()" is new to me, can you explain Walter? Ed == Quote from Walter Bright (newshound1 digitalmars.com)'s articleEd wrote:Found the trouble maker, it happens when you define a table > 1 million entries, for instance: #define EOC_MAX 1000000 static unsigned int hkw [EOC_MAX]; Now raise EOC_MAX to 2 million and the linker crashes. Hoping for a solution....The easiest solution is to new() the array, rather than statically allocate it.
Apr 20 2007
Ok, will find my way around. But, are you going to fix the linker problem? I mean, compiling with DOSX no such problems do occur. Thx again for excellent support & compiler. Ed (ex Zortech user)new() is C++. If you're using C, you can use malloc() instead. Ed wrote:How to "new()" is new to me, can you explain Walter? Ed1Ed wrote:Found the trouble maker, it happens when you define a table >staticallymillion entries, for instance: #define EOC_MAX 1000000 static unsigned int hkw [EOC_MAX]; Now raise EOC_MAX to 2 million and the linker crashes. Hoping for a solution....The easiest solution is to new() the array, rather thanallocate it.
Apr 21 2007
Walter Bright <newshound1 digitalmars.com> Ed wrote:Ok, will find my way around. But, are you going to fix the linker problem? I mean, compiling with DOSX no such problems do occur. Thx again for excellent support & compiler. Ed (ex Zortech user)It won't be fixed in the near future.
Apr 22 2007