Stack trace (x64):8C2F9E -- Range check error.

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
kkimber
Junior Member
Junior Member
Posts: 18
Joined: 2009-05-30, 05:08 UTC

Stack trace (x64):8C2F9E -- Range check error.

Post by *kkimber »

---------------------------
Total Commander 9.20ß1
---------------------------
Range check error.
Range check error
Windows 10 Enterprise 10.0 (Build 17134), base: 0400000

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Stack trace (x64):8C2F9E

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes No
---------------------------
User avatar
Stefan2
Power Member
Power Member
Posts: 4133
Joined: 2007-09-13, 22:20 UTC
Location: Europa

Re: Stack trace (x64):8C2F9E

Post by *Stefan2 »

kkimber wrote:...

, with a description of what you were doing when this error occurred!

...






 
User avatar
tuska
Power Member
Power Member
Posts: 3741
Joined: 2007-05-21, 12:17 UTC

Post by *tuska »

According to an email from Mr. Ghisler, the problem "Range Check Error" will be fixed in Beta 2.
See also: viewtopic.php?p=340665&sid=43fcdb68b4f293a24265cf7527c6dd71#340665
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

This should be fixed in TC 9.20 beta 2, please test it!
Author of Total Commander
https://www.ghisler.com
User avatar
deus-ex
Power Member
Power Member
Posts: 969
Joined: 2003-02-10, 17:45 UTC

Post by *deus-ex »

Like tuska referred to this thread, the condition that triggered the "Range Check Error" for me was fixed with 9.20ß2.

However, since using 9.20ß2 I experienced the "Range Check Error" again under different conditions, as I described in the mentioned thread. Unfortunately I was not able to reproduce the error which makes it quite difficult to fix.

There is another condition related to RAR multipart-archives that can trigger a "Range Check Error", reported here.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I don't think that they are directly related. So far I couldn't reproduce either of these two.
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

OK, I finally found out what is causing this! I switched from Windows 7 to 10 - not as an update, but as a parallel installation. When doing this, some settings of the Lazarus/FPC compiler were lost, and the library (but not Total Commander itself) was suddenly compiled with range checking on. Turning that off seems to fix all remaining range check errors.
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

This should finally be fixed in beta 3, please test it!
Author of Total Commander
https://www.ghisler.com
User avatar
deus-ex
Power Member
Power Member
Posts: 969
Joined: 2003-02-10, 17:45 UTC

Post by *deus-ex »

After using beta 3 regularly since two days I can confirm that the issues I reported in this thread appear to be finally fixed. Thanks, Christian.
Post Reply