[英]Fortify Translator severe error: specified path, file name, or both are too long
While translating a C# solution with fortify 18.10 , on the Developer Command Prompt for VS 2017 , i get the following error on the sca.log : 在VS 2017的开发人员命令提示符上翻译带有fortify 18.10的C#解决方案时,我在sca.log上收到以下错误:
[2019-11-26 11:10:21.078 Thread-16 SEVERE 1103] Translator execution failed. [2019-11-26 11:10:21.078线程16 SEVERE 1103]转换器执行失败。 Please consult the Troubleshooting section of the User Manual. 请查阅用户手册的“故障排除”部分。 Translator returned status -2147024690: 转换器返回状态-2147024690:
DOTNET-DEBUG: Unhandled exception: The specified path, file name, or both are too long . DOTNET-DEBUG:未处理的异常: 指定的路径,文件名或两者都太长 。 The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. 完全限定的文件名必须少于260个字符,目录名称必须少于248个字符。
The command issued is: 发出的命令是:
"C:\Program Files\Fortify\Fortify_SCA_and_Apps_18.10\bin\sourceanalyzer.exe" -b test-build-id-48df2a2423671960b5f911260f922c3a0e50807f devenv MySolution.sln /REBUILD debug
On the log, before the SEVERE
message, only files way under 248 characters are handled. 在日志上,在SEVERE
消息之前,仅处理248个字符以下的文件。
The problem is that the build-id
get concatenated to other file names, without any log of the file being outputted. 问题是, build-id
被串联到其他文件名,而没有输出该文件的任何日志。
It's important to shorten the build identifier. 缩短构建标识符很重要。
With the name test-48df2a2
source analyzer will complete the execution. 使用名称test-48df2a2
源代码分析器将完成执行。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.