Enhance dynamic libraries loading related error messages [CORE5908] #6166
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff Messages are enhanced except deprecated UDFs and unfortunately ICU - in case of failure ICU is attempted to be loaded >50 times and reporting all errors to user is definitely unreal. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] Fix Version: 3.0.4 [ 10863 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Cannot be tested => Done successfully Test Details: Thanks to Alex for suggestion about implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @AlexPeshkoff
Due to wrong initial design of class ModuleLoader errors displayed when loading library fails miss OS-specific information about a reason of a failure (no such file, invalid format, unresolved external reference, etc.), they only say - module/library not loaded. This makes fixing related bugs extremely problematic in many cases.
Errors reported should be extended in order to show exact reason of a failure.
Commits: 6a63c3b 2d973b9
====== Test Details ======
Thanks to Alex for suggestion about implementation.
The text was updated successfully, but these errors were encountered: