topic That makes sense. For some in Analyzers

Finding hotspot tutorial related issue

Athira_A_ — Tue, 21 Apr 2015 06:50:35 GMT

As per the Tutorial: Finding Hotspot, I could Build application and create new project, Run Basic Hotspots Analysis, Interpret Result Data. But while trying to Analyze Code and edit the most hotspot region of the code, I was unable to open the editor from Open Source File Editor icon. It was showing "Cannot Open the external text file editor for this file."

I had also given $ "export EDITOR=gedit" command in the terminal before running amplexe-gui. Kindly help me with the issue and suggest me how to get access to the editor.

Thank You.

How are you starting VTune

David_A_Intel1 — Tue, 21 Apr 2015 20:39:08 GMT

How are you starting VTune Amplifier, from the Ubuntu GUI or from a console window? If you started it from the Ubuntu GUI, you need to set a 'system-wide' environment variable, e.g., EDITOR. VTune Amplifier is going to inherit the environment from the system.

If from a console window, did you set the EDITOR environment variable in the same console window and prior to starting amplxe-gui? Also, if you enter 'gedit' at the console prompt, does gedit start?

I am having the same issue as

cole_b_ — Tue, 16 Feb 2016 19:33:09 GMT

I am having the same issue as above. When I double click on a line of code or click "Open Source File Editor", it produces the same error about not being able to open the external text editor. I am launching from the terminal with "sudo ./amplxe-gui". Before I do that, I run "export EDITOR=gedit". I can then open gedit with "gedit". I have also tried setting the VISUAL variable to gedit as well as restarting and re-assigning the EDITOR variable.

Any idea what is going on?

Thanks

Hi cole:

David_A_Intel1 — Tue, 16 Feb 2016 20:29:03 GMT

Hi cole:

I suspect the 'sudo' is creating a new shell and not inheriting the variable you defined. Try this: create a script that exports the variable and then starts VTune Amplifier; now 'sudo <script'.

That makes sense. For some

cole_b_ — Wed, 17 Feb 2016 14:34:59 GMT

That makes sense. For some reason I thought running it without sudo was giving me problems, but I'm not seeing any right now. The editor now works.

Thanks