-[8.50b3] Access viol. while using Plugin

[ferhat]

I am not sure how TC handles exceptions, when they occur inside a loaded plugin. I have seen a stack trace dialog while using the VSS file system plugin (Link is below).

Environment: WinXP 32Bit SP3
Steps to reproduce:

1) Be sure that "Create a log file" is turned off [Configuration]->[Log file]

2) Install VSS Addon (I am using it with VSS 6.0)
http://www.totalcmd.net/plugring/vss.html

3) Configure the addon to point to existing VSS DBs (don't know if this is required)

4) Restart TC

5) Select "Network Neighborhood"

6) Enter "vss" to see existing databases

7) Go to [Configuration]->[Log file] and turn "Create a log file" on and
click on Apply.

observed:
Stack trace window is shown with following information:

---------------------------
Total Commander 8.50b3
---------------------------
Exception in vss.wfx:FsFindFirst!
Access violation at address 01B04B09. Read of address 43737961
Windows XP SP3 5.1 (Build 2600)

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

Windows exception: C0000005
Stack trace:
01B04B09
>66B0FC 6071C0 60BC8E 64872C 648A50 44630D
44825E 42569C 44781F 42569C 5A8396 5A843C
446444 4362DE 44630D 4478E1 44624B 448612
44825E 42569C 44781F 42569C 44778D 42569C
4478E1 44825E 42569C 44781F 42569C 42AD58
42ADF4 59E5E4 65BA1C 65DC6F 42DB2A 44630D
44825E 42569C 44781F 42569C 42AD58 42ADF4
6F86D7
Raw:
66A7EB 6F5677 6F5677 6F5733 5CD165 6F006A
42569C 64AC63 64B16B 5F0065 750065 402E4A
402E4A 66359E 427378 4478E1 44825E 448281
42569C 6F588F 6EE464 6F006A 44781F 42569C
67E522 6F5733 67FE31 61006D 62005D 6F588F
6EE464 6F588F 6EE464 44778D 42569C 4485D7
44852D 470051 6E006D 6E006D 4D004D 4026A0
4023C7 4023EF 4026B8 4036C1 66A124 6F5677
667EC2 6E006D 610070 690069 44778D 42569C
4485D7 44630D 44852D 44852D 4375EA 44781F

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------

[gdpr deleted 6]

Unfortunately, you will have to contact the plug-in author regarding your problem.

TC's plugins are just DLL with native code. And if this native code in the plug-in decides to crash, there is little to nothing Total Commander can do about it.

[ghisler(Author)]

Indeed you will need to contact the plugin writer. TC just reports excceptions in plugins so they can be fixed.

[ferhat]

Ok therefore it's not a TC issue.
I was not sure if the error handling behavior was as expected.