Runtime Error 216
Posted: Wed Sep 27, 2017 12:11 pm
Our software is currently using the latest version of MadExcept and on one of our Q/A test PCs we are seeing a vary occasional Windows Runtime error 216 dialog on the screen.
Our software is structured as a number of dll's each of which is instantiated with a LoadLibrary inside of a host application. A seperate instance of the host application is spawned for each dll to be loaded.
All are compiled as 32bit Delphi code using Berlin.
The dll's each have madexcept enabled with a unique bugreport filename and the host process also has madexcept enabled but uses the same bugreport name for all instances.
The dll's and the host process reside in the same folder.
I have verified using MadTraceProcess that all processes are present in the list of processes to be traced so I am sure the MadExcept features are enabled.
Firstly is this a valid configuration when using MadExcept, or should we locate each dll and a copy of the hostprocess in seperate sub folders to avoid potential conflicts writing to a shared bugreport file ?
One of the Dll's does use a COMWrapper to instantiate a vendor API written in .Net however the wrapper does have exception handling and is set to capture all first chance exceptions and route them through a common OnError event for logging purposes. Additionally the Windows Event viewer indicates that the Runtime Error occurred in the hostprocess excutable.
Under what circumstances would the above Runtime error avoid being captured by MadExcept and routed to the bug report file ?
Our software is structured as a number of dll's each of which is instantiated with a LoadLibrary inside of a host application. A seperate instance of the host application is spawned for each dll to be loaded.
All are compiled as 32bit Delphi code using Berlin.
The dll's each have madexcept enabled with a unique bugreport filename and the host process also has madexcept enabled but uses the same bugreport name for all instances.
The dll's and the host process reside in the same folder.
I have verified using MadTraceProcess that all processes are present in the list of processes to be traced so I am sure the MadExcept features are enabled.
Firstly is this a valid configuration when using MadExcept, or should we locate each dll and a copy of the hostprocess in seperate sub folders to avoid potential conflicts writing to a shared bugreport file ?
One of the Dll's does use a COMWrapper to instantiate a vendor API written in .Net however the wrapper does have exception handling and is set to capture all first chance exceptions and route them through a common OnError event for logging purposes. Additionally the Windows Event viewer indicates that the Runtime Error occurred in the hostprocess excutable.
Under what circumstances would the above Runtime error avoid being captured by MadExcept and routed to the bug report file ?