New cmd window spawned when run from TeamCity in Windows

[Hill__Stephen]

We are running the following in cmd under Windows:

"C:\Program Files (x86)\IntelSWTools\Inspector 2019\bin64\inspxe-cl.exe" -user-data-dir=build\\unittest64 -collect mi3 -knob detect-invalid-accesses=true -knob analyze-stack=false -knob detect-leaks-on-exit=false -knob detect-resource-leaks=false -knob enable-memory-growth-detection=false -knob enable-on-demand-leak-detection=false -knob remove-duplicates=true -knob still-allocated-memory=false -knob stack-depth=32 -mrte-mode=auto -module-filter-mode=include -s-f ../tm_win32_tools/cpputest/inspector_cpputest.sup -r seg_unittest.exe.inspector -- build\unittest64\seg_unittest.exe

And the output from the .exe under test, seg_unittest.exe, comes out with output of Inspector in the cmd. All good :).

If we run the same cmdline with Teamcity Agent batch, Inspector spawns a new cmd shell under which the output of seg_unittest.exe comes out. The problem with this is that we then cannot capture this output in TeamCity.

Why do we see this behaviour under TeamCity?

How can we fix it?

[James_T_Intel]

Is it possible that you are running into the problem described at https://stackoverflow.com/questions/19636433/teamcity-command-line-build-does-not-actually-start-the-cmd-file?  If so, Inspector cannot bypass this behavior.  If you want to capture the command line output, I recommend redirecting to a text file and post-processing that file.