- Download Process Monitor: https://learn.microsoft.com/en-us/sysinternals/downloads/procmon#download
- Launch the tool and choose the menu "Filter / Organize Filters"
- Import the file "configure inject.PMF" in attachment
- Now, choose the menu "Filter / Load Filter" then "configure inject", the filter will be applied
- In the results, take a look at the column "Path" to know where ps_windows_dllinject.dll should be copied.
Why do I get an error like "cannot open shared object file: ps_windows_dllinject.dll" using polyspace-configure?
35 ビュー (過去 30 日間)
古いコメントを表示
MathWorks Support Team
2023 年 8 月 7 日
編集済み: MathWorks Support Team
2024 年 11 月 13 日 11:17
When using polyspace-configure to prepare my project for Polyspace analysis, I get a fatal error message like the following, and the build process halts. How can I fix the issue to allow polyspace-configure to succeed in tracing my build command?
polyspace-configure: 0s: DEBUG: Emitting injection order for process xxx.yyy
0 [main] mkdir <yyyy> <pathto>\win64\x86_64\usr\bin\mkdir.exe: *** fatal error - error while loading shared libraries: /c/Program Files/Polyspace/R2019b/polyspace/configure/win64/ps_windows_dllinject.dll: cannot open shared object file: No such file or directory
35748 [main] mkdir <xxxx> cygwin_exception::open_stackdumpfile: Dumping stack trace to mkdir.exe.stackdump
Makefile:55: recipe for target 'file.o' failed
make: *** [pathto/src/file.o] Error 256
採用された回答
MathWorks Support Team
2024 年 11 月 13 日 0:00
編集済み: MathWorks Support Team
2024 年 11 月 13 日 11:17
This is the symptom of a polyspace-configure issue related to a Cygwin's executable like "make.exe" or "tee.exe", executable used during the build process.
A workaround is to create the missing folder and copy the file "ps_windows_dllinject.dll" (that can be found in <Polyspace installation>/polyspace/configure/win64) into this new folder.
To know the folder to create, you can use the tool Process Monitor (from Microsoft) to see which paths are being referenced during the build process.
To help you apply this workaround, a predefined filter for Process Monitor, specifically targeting the location of the DLL, is attached to this article.
Here is the procedure:
0 件のコメント
その他の回答 (0 件)
参考
カテゴリ
Help Center および File Exchange で Options at Command Line Only についてさらに検索
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!