Target Deployment Technology
If you are experiencing problems related to implementing a TDP on a particular target, the following troubleshooting guide might help you to find a solution.
If a problem persists, do not hesitate to contact IBM Customer support for help.
Problem |
Solution |
In breakpoint mode, the priv_exit breakpoint is never reached |
The priv_exit breakpoint is only reached when problems are found by the TDP. See Breakpoint mode in Target system categories. |
When using Runtime Analysis tools alone, no results are produced and the atl_obstools_dump function is never reached. |
This usually occurs when the application never ends or when the entry point is not a main function. |
When using Runtime Analysis tools alone, no results are produced and the application uses a custom exit function instead of the standard function. |
Add the following line to the ANA ? #pragma attol exit_instr = "exit","<ExitFunction>" |
When using Runtime Analysis tools alone, no results are produced and the application does not use main as an entry point. |
When using main as an entry point, the instrumentor automatically adds a call to the dump at the end of this procedure. If you do not use main as an entry point or if this file has not been instrumented then this call is not generated. The solution is the same as for an application which never exits. See Never ending applications. |
When using Runtime Analysis tools alone, no results are produced although the atl_obstools_dump function is reached. |
Check that in the Initialized global variable support and checks section of the TDP the initialization is supported. If not then unset RTRT_VARIABLE_INIT_SUPPORTED. Check that memory is reintialized to 0 before execution. If not then set RTRT_RAM_SET_RAMDOMLY. |
When using Runtime Analysis tools alone, no results are produced and in breakpoint mode, the priv_close breakpoint is never reached. |
The priv_close breakpoint is executed at the end of the execution to close the result file. If however atexit is not set to NONE, then priv_close is not explicitly called. If the exit function does not perform the call, change the TDP to set atexit to NONE. |
When I collect coverage data for a component test, either:
|
The #line x statements are not generated properly by the compiler in the .i file. Find the compiler option to properly generate these #lines during the preprocessing phase. |
I cannot tell whether my compiler is supported. |
We have never encountered any problems supporting any C compiler whatsoever with target deployment port technology. This, however, is not true for all C++ compilers. For example, Borland C++ is not supported. |
There is no TDP for Memory Profiling for Java |
Memory Profiling for Java uses the JVMPI mechanism provided by the JVM and does not rely on target deployment port technology. If JVMPI is not available, for example with J2ME, there is no way to perform memory analysis. In this case, there are two options: - Implement your own JVMPI mechanism on the target JVM. - Implement another means of tracking memory usage on the target |