[9.20ß1] TC 64bit Range Check Error

[ghisler(Author)]

Thanks, I had to half the numbers on my 96dpi display to get the error. What happens is that one of the widths or heights of the controls becomes negative, causing the range check error in Lazarus. Delphi just ignores the error. I will manually limit the sizes to 0 or larger.

[deus-ex]

Christian, you are welcome. I still don't grasp how only the combination of those three parameters would trigger the error, especially how "RedirectSection=0" is involved into this issue is what baffles me the most.

Anyways, looking forward to the next beta with this issue fixed.

[ghisler(Author)]

I'm getting it also without RedirectSection=0. Maybe you have a line starting with AlternateUserIni= in your [configuration] section? Only then the RedirectSection=0 has any effect.

[deus-ex]

Yes, I do make use of "AlternateUserIni=" for specific sections like command-line history, search, rename, etc. which helps to avoid cluttering wincmd.ini over time.

[ghisler(Author)]

That explains why you had to use AlternateUserIni=0, otherwise the width and height in that section would be ignored.

[deus-ex]

I don't use "AlternateUserIni=0" but "AlternateUserIni=tc.ini". Probably you meant to say "that's why you had to use RedirectSection=0"?

[deus-ex]

After identifying the root cause of the "Range Check Error" I removed the ill fated two entries "dx=" and "dy=" from wincmd.ini and started to use 9.20ß1 64-bit regularly. After a few hours of normal use the "Range Check Error" hit me again, twice.

Code: Select all

---------------------------
Total Commander 9.20ß1
---------------------------
Range check error.
Range check error
Windows 10 Professional 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   
---------------------------

Answering the prompt with "yes" allowed me to continue from the state the error poped up, the file panes still seem to behave normally. Yet I immediately went back to stable release 9.12 as this is far to unsafe to continue.

Checking my wincmd.ini I could not find any trails of the previously removed entries "dx=" and "dy=", so there are certainly more unidentified issues with the change from Delphi to Lazarus.

[ghisler(Author)]

You don't need to report any more "range check error" bugs until beta 2. I think I found the problem and will apply a bugfix.

[ghisler(Author)]

This should be fixed in TC 9.20 beta 2, please test it!

[deus-ex]

I have been using TC 9.20ß2 for a day now without any issues. Also I just successfully retested a wincmd.ini containing the three entries which previously lead to the "Range Check Error" at start up. This bug appears to be fixed.

Thank you for the quick turn around, Christian, it's much appreciated.

[ghisler(Author)]

Thanks, please let me know immediately if it occurs again.

[deus-ex]

I'm sorry that I actually have to answer your request.

Just got another "Range Check Error". It appeared after renaming a file extension, then immediately pressed [End] to jump to the end of the directory containing 526 files and 2 subdirectories at the time the error occured.

Confirming the error prompt with "yes" I was able to continue working with TC. I directly tried to retrigger the error by redoing the same steps, however without success.

If it helps you to identify the issue by providing me with a special debugging version that logs all operations, I'm glad to support.

[ghisler(Author)]

Sorry, cannot reproduce so far.

[deus-ex]

That's why I suggested that you probably should offer some sort of debugging version for users willing to assist. At this time I also cannot reproduce the bug, yet it has happened for reasons currently unknown.

[deus-ex]

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