Executable-of-Interest process ID for Problems

Executable-of-Interest process ID for Problems

Hello,

We have a Python script running same executable with different parameters. So we set up our command-line:

/opt/intel/inspector_xe_2013/bin64/inspxe-cl -collect mi2 -user-data-dir intelinspector_results -result-dir {at}_@@@ -executable-of-interest <executable> -- /usr/bin/python test_loop.py test_jobs.txt

The Python script test_loop.py will run the executable-of-interest multiple times while the Inspector detects and collects memory error to a single result directory.

It would be useful if we could tell from the Inspector report which 'run' a particular problem came from. Each 'run' is an instance of starting the executable-of-instance with a different parameter, and resulting in a different process-ID.

Thanks,

Frankie

4 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

IXE will fully instrument and collect data for only one instance of the executable-of-interest.  To collect for multiple instances, you need to invoke the IXE collection from within test_loop.py.

Hello,

The Python script runs the executable-of-interest multiple times (serially, not in parallel). The Inspector is able to collect the memory issues from all the runs. But that results in a single report. Is there a way to associate a reported issue to particular run(s), such as process-ID?

Thanks,

Frankie

I reproduced the behavior with recording data for multiple instances of the executable-of-interest.  It's not supposed to do that.  Even though the collector may collect info for multiple runs, the rest of the product does not store the association between an issue and the originating process ID or command line.    To get the information about which run produces which issue, you should do separate collections inside test_loop.py.

Login to leave a comment.