Access violation

[yurik]

On a network share, selected and queued some files for copying to a local harddrive. Tried to navigate to a different directory with many files, and got this.

---------------------------
Total Commander 7.56a
---------------------------
Access violation at address 14458B00. Read of address 14458B00.
Access violation at address 14458B00. Read of address 14458B00
Windows 7 6.1 (Build 7600)

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

Windows exception: C0000005
Stack trace:
14458B00
4023DB 4026A4 5F7A3D 620F39 5F6775 444F62
422CC0 422CC0 6859B8 4F8AD8 432F32 432C14
444491 422CC0 444F62 422CC0 444523 422CC0
5495FC 445A9F 443011 444F62 >422CC0 444523
422CC0 42838C 428424 6C53C9
Raw:
5F5AE0 6C2368 6BB900 4E38E5 444491 422CC0
4452DB 443011 445231 4445E5 444F62 444F85
422CC0 444523 422CC0 6C2260 6BBE5B 6878FD
68D5E4 61F471 68D5E4 61F471 68692C 5F9A43
6C4879 5FA817 67D3C2 5FD757 5FD77A 422CC0
4452DB 443011 445231 4348C2 4445E5 444F62
444F85 422CC0 444523 422CC0 4023DB 4026A4
4036AD 5F9A09 443E58 443E97 443F66 443F82
443FC9 4458F7 434B2B 449D78 402E36 443011
445231 4348C2 4445E5 444F62 444F85 422CC0

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes No
---------------------------

[ghisler(Author)]

I will analyze it, thanks!

[Usher]

All unspecified access violation problems reported here are probably caused by UTF-8 strings in wincmd.ini file. And it is because of TCmd bug, not manual file editing.
A good example is directory history - TCmd writes directory path as UTF-8 string started with BOM. It looks like that below:

Code: Select all

[RightHistory]
1=[BOM]C:\Some path\to\directory\with\non-ASCI\UTF-8 encoded\characters\
2=[BOM]D:\Some other path\to directory\with non-ASCI\UTF-8 encoded\characters\
3=[BOM]C:\Ścieżka\do katalogu\z ogonkami\źęć żąśńół\ 

Let's see what is described in topics I found using search for "Access violation".

Here are reports on non-ASCII characters in folder name:
1. This topic (On a network share, selected and queued some files...)
2. Crash when retrying folder renaming on network share
3. TC crashes when copying files using Ctrl+C, Ctrl+V
4. Error renaming files
5. AV while copying
6. Crashes when browsing thru folders and copying files
7. Crash under XP SP2 (I've opened breadcrumb menu...)

And here is a topic with just access violation report - UTF-8 strings are already present in wincmd.ini:
1. Crash under Windows Server 2008 R2

I just tested TCmd 7.55a and it has no problem with UTF-8 strings added by TCmd 7.56a so I recommend to stay with 7.55a until the bug will be fixed.

[ghisler(Author)]

I have never heared of any problems with the BOM inside the ini, but you can easily check whether this is the problem or not. Just load the file in notepad and save it as type "Unicode" (=UTF16). Then TC doesn't need to use these BOM headers.

[Usher]

I have never heared of any problems with the BOM inside the ini,

It doesn't mean the problems don't exist. Do you use letters with umlauts in directory names?

but you can easily check whether this is the problem or not. Just load the file in notepad and save it as type "Unicode" (=UTF16).

It's not a portable solution - it works only in NT family (Win2k/XP/Vista/7). What to do in Win9x?

[ghisler(Author)]

Win9x cannot access Unicode names anyway, so you should avoid paths with them at all cost.

[Usher]

Once again - it's not a solution if you want to use TCmd as a portable software. You cannot be sure what OSes and what names have PCs where you must use your pendrive with TCmd.
If you try to use Tcmd with ANSI ini, it will have troubles in NT family and with UTF-16 ini it won't work at all in Win9x. The only workaround by now is to call TCmd with different inis as command line parameters.