You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The discussion there suggests that passing "-no-pie" while compiling allows profiling of applications that were previously giving "not a valid application" error
On Oct 4, 2017, at 4:12 PM, Chris Hesik ***@***.***> wrote:
Can you try this with RCP 5.2?
Earlier versions of RCP check to see if the file being profiled is a valid ELF executable. This check was relaxed in RCP 5.2.
See #2 <#2>
The discussion there suggests that passing "-no-pie" while compiling allows profiling of applications that were previously giving "not a valid application" error
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH4Lcl0P2uZb4S_T_0KeMUO06jr_IEeLks5so_TWgaJpZM4PuLxp>.
I am trying to profile HSA applications on a discrete GPU node.
Rocm 1.6; Radeon Compute Profiler (rcprof) 64 bits - V5.1.6400.
I copied the vector copy example in rocm/hsa. Built and ran the code. It ran fine. When I try the profiler, I get a "not a valid application" message.
(t1)%rocm-profiler -C ./vector_copy /home/apan/code/dlbench/opencl/vcopy/sample/./vector_copy is not a valid application
I am getting similar errors with other applications as well. Probably some flag I need to pass in the build process?
The text was updated successfully, but these errors were encountered: