I get this error when trying to create a callgraph for the compiler. If I remove some of the arguments to mcpcom the error goes away.
vtl activity -c callgraph -app mcpcom,-p,--bool,timing.cpp -moi mcpcom run VTune Performance Analyzer 1.0 for Linux* Copyright (C) 2000-2002 Intel Corporation. All rights reserved.
The Activity is running. The Activity failed to stop callgraph collector, because there are no valid exe controllers associated with the collector.
Unable to run the activity because an appropriate EXE controller could not be created. This is probably either because a specified remote system could not be found or because a specified remote system is not properly configured.
Well that helped me get started but now I get an internal error:
n=800 timing.cpp" -moi mcpcom run VTune Performance Analyzer 1.0 for Linux* Copyright (C) 2000-2002 Intel Corporation. All rights reserved.
The Activity is running. Wed Feb 26 17:49:59 2003 Static instrumentation started
Discovery Summary: Found 18775 procedures. Fail to instrument 3 of them. Found 1 additional functions. Fail to instrument 0 of them. Wed Feb 26 17:50:30 2003 All functions instrumentation of module mcpcom was successful. Wed Feb 26 17:50:30 2003 None instrumentation of module ld-2.2.4.so was skipped. Wed Feb 26 17:50:30 2003 Exports instrumentation of module libc-2.2.4.so was skipped. Wed Feb 26 17:50:30 2003 All functions instrumentation of module libm-2.2.4.so was skipped. Wed Feb 26 17:50:30 2003 Static instrumentation done Wed Feb 26 17:50:33 2003 Data collection started... Intel C++ Compiler for 32-bit applications, Version 8.0 Pre-Beta Build x Built Feb 26 2003 16:14:38 by jward4 on nht6011.spt.intel.com in /home/nsl/jward4/cmplr/dev_cfe/dev Copyright (C) 1985-2003 Intel Corporation. All rights reserved. (0): internal error: #0_3645: catch entry list and handler info list differ in length (shared/ip/ipo_inl.c, line 3645)
BTW, thanks for posting this one. The way in which vtl was invoked in the initial post should have been interpreted as a syntax error by vtl--however, the input was accepted and resulted in the weird message having to do with EXE Controllers.
This has been fixed, and the fix will be available in the next release of the product.