This seems like a simple operation, but I'm having difficulty finding instruction on how to do it.So, I've got a script that runs Main.exe through a number of operations, and there's various memory issues with this particular set of operations. However, I don't care about memory leaks/problems outside of a single problematic DLL (Leaky.dll), so I want Inspector XE to completely ignore memory leaks/problems everywhere else. I'm running Inspector XE through the command line, and the command I have recently used is as follows: inspxe-cl -collect mi1 -module-filter-mode=include -module-filter="path/to/Leaky.dll" -- "path/to/Main.exe" -runTest From reading the info in the command line help, I assumed that the -module-filter-mode=include and -module-filter="path/to/Leaky.dll" would be sufficient to single out this bad DLL. However, when I look at the results, there is no information related to Leaky.dll. I'm guessing that I'm misusing the module filter switches somehow, but I'm not sure exactly how. Any guidance is greatly appreciated. EDIT: I realized that I made a mistake in my path, and I am now seeing leaks in Leaky.dll. However, there is still a large number of leaks noted in other modules, mscorwks.dll for example. I would like to ignore these, as they make up the vast majority of leaks, and contribute to the 100,000 leak-limit being reached on a given run
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.