Archives Discussions

[Raistmer]

Example:
sprofile.exe "C:\Program Files\ATI Stream\Tools\ATI Stream Profiler 1.4\x86\MB_6.10_win_SSE3_ATI_r132e.exe" "-period_iterations_num 2"

stderr:
....
11:53:35 (932): Can't set up shared mem: -1. Will run in standalone mode.
Priority of worker thread raised successfully
....

MB_6.10_win_SSE3_ATI_r132e.exe -period_iterations_num 2

stderr:
....
11:55:22 (5340): Can't set up shared mem: -1. Will run in standalone mode.
Number of period iterations for PulseFind setted to:2
Priority of worker thread raised successfully
....

That is, app recognize command line parameter if run w/o profiler and does't recognize it running under profiler.

[bpurnomo]

Thank you for the bug report.  We confirm that this is a problem with the profiler.  The problem is that the profiler alters the position of the command line arguments by one for the application when it launches the application.  This problem will be fixed in a future release of the profiler.

For now, as a workaround, you should be able to launch your application as follows:

sprofile.exe "C:\Program Files\ATI Stream\Tools\ATI Stream Profiler 1.4\x86\MB_6.10_win_SSE3_ATI_r132e.exe" "-PADPOSITION -period_iterations_num 2"

assuming that the -PADPOSITION is not used as a command line option by your application.

Please let us know whether this workaround works for you.

[Raistmer]

Originally posted by: bpurnomo

Thank you for the bug report.  We confirm that this is a problem with the profiler.  The problem is that the profiler alters the position of the command line arguments by one for the application when it launches the application.  This problem will be fixed in a future release of the profiler.




For now, as a workaround, you should be able to launch your application as follows:




sprofile.exe "C:\Program Files\ATI Stream\Tools\ATI Stream Profiler 1.4\x86\MB_6.10_win_SSE3_ATI_r132e.exe" "-PADPOSITION -period_iterations_num 2"




assuming that the -PADPOSITION is not used as a command line option by your application.




Please let us know whether this workaround works for you.

Yes, this workaround works OK, now I can use profiler as intended, thanks.