Is it true that the released version cannot load third-party plugins? #2544
Replies: 1 comment
-
The names were causing false positives since they shared the same prefix as the SDK from Process Hacker.
Debug builds have named exports to make debugging easier
We were testing this with the canary branch but it's disabled.
No |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I wrote a plugin and discovered that among the recent versions, only
3.2.25116.2104seems capable of loading my plugin, while others cannot.Using DependenciesGui.exe to inspect the exported symbols of
SystemInformer.exe,I found that in all versions (except 3.2.25116.2104), the symbols have been transformed into forms like
Original_\d\d\d\d.However, the exported symbols of the
SystemInformer.exeI compiled all have original function names.I noticed that it seems to be the function
ExportDefinitionsintools\CustomBuildTool\Build.csthat processes the exported symbols:systeminformer/tools/CustomBuildTool/Build.cs
Lines 1706 to 1770 in 08dbe56
In the release versions, the exported symbols are random, which seems to prevent third-party plugins from locating the correct function positions.
Does this mean that developing plugins must require merging into the official codebase?
I am not very skilled in Windows and C++, so the plugin I created uses Dart/Flutter-related technologies. Therefore, I feel that merging it into the official repository is unlikely.
Beta Was this translation helpful? Give feedback.
All reactions