Long Story (This is X)

I need to start CLion with sudo so that I can attach gdb to the running process from CLion (for a debugging purpose). The reason is because when I run CLion without sudo, and trying to attach to a process (CLion GUI), I receive:

com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$GDBCommandException: ptrace: Operation not permitted.

As a second check, I tried running gdb in the terminal manually without sudo:

gdb -p 16741

...

Could not attach to process. If your uid matches the uid of the target process, check the setting of "/proc/sys/kernel/yama/ptrace_scope", or try again as the root user. For more details, see "/etc/sysctl.d/10-ptrace.conf"

ptrace: Operation not permitted.

However, if I run gdb with sudo:

sudo gdb -p 16714

...

Attaching to process 16714

So I think I should run CLion as root.

TLDR / The Problem (This is Y)

Now, if running sh /opt/clion/bin/clion.sh from the Ubuntu terminal, CLion does pick up the environment variables sourced in the ~/.bashrc file, and my program compiles with no error.

But because without sudo, I can't attach gdb to the process from within CLion for my debugging purpose, so I need to run the clion.sh startup script as root.

The problem is that when running sudo sh /opt/clion/bin/clion.sh, CLion doesn't seem to pick up the environment variables, leading to "CMake cannot find package ..." error, which makes my program not runnable⁠—worse.

CMake Error at CMakeLists.txt:64 (message):
  find_package(catkin) failed.  catkin was neither found in the workspace nor
  in the CMAKE_PREFIX_PATH.  One reason may be that no ROS setup.sh was
  sourced before.

Question

How do I run the CLion startup script with sudo, and preserve the environment variables that are sourced in ~/.bashrc?

If relevant

• I think CLion doesn't pick up the following variables. To be very specific, I have this line in my ~/.bashrc file:

  source /opt/ros/kinetic/setup.bash
  

  whose content is

  #!/usr/bin/env bash
  # generated from catkin/cmake/templates/setup.bash.in
  
  CATKIN_SHELL=bash
  
  # source setup.sh from same directory as this file
  _CATKIN_SETUP_DIR=$(builtin cd "`dirname "${BASH_SOURCE[0]}"`" > 
  /dev/null && pwd)
  . "$_CATKIN_SETUP_DIR/setup.sh"
  

  Perhaps, there might be a way to add this directly to the startup script of CLion?

• XY Problem
• I am running Ubuntu 16.04

I'm trying to set GCC as Clion c++ compiler from settings, but I found many gcc files like : gcc, gcc-8, gcc-ar, gcc-nm, and I don't know which one to attach in c++ compiler in Toolchain. I'm totally new to Ubuntu and Clion also.

Ctrl-Shift-F (find in files) doesn't work in CLion in KDE. How to fix?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

I've been struggling with this for ~2 days now and I can't seem to find the solution. I recently switched to a new laptop and installed Ubuntu 19.04, and now something with my c++ compiler is not working. I'm trying to load the CMakeLists.txt file in CLion using the GNU compiler from here, but I keep getting the following error message:

-- Add a local project.cmake file to add your own targets.
-- Configuring done
You have changed variables that require your cache to be deleted.
Configure will be re-run and you may have to reset some variables.
The following variables have changed:
CMAKE_C_COMPILER= /usr/bin/arm-none-eabi-gdb

-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/arm-none-eabi-gcc

And eventually these lines:

arm-none-eabi-g++: error trying to exec 'cc1plus': execvp: No such file or directory

arm-none-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory

On my old (working) laptop it says:

-- The C compiler identification is GNU 6.3.1
-- The CXX compiler identification is GNU 6.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/arm-none-eabi-gcc

I've checked many forum posts, but I can't get it to work. There are many things I've tried many things, including:

sudo apt-get install --reinstall build-essential

The following command:

g++ --print-prog-name=cc1plus

Returns:

/usr/lib/gcc/x86_64-linux-gnu/8/cc1plus

And this:

which arm-none-eabi-g++

Returns:

/usr/bin/arm-none-eabi-g++

But:

which cc1plus

Returns nothing.

I feel like there should be a simple fix that points CLion to the right cc1 compilers, but the toolchain settings are the same as on my working laptop, but the new CLion doesn't work. Any help is greatly appreciated.

Jack

EDIT:

This is how the CMake is set

CMAKE_MINIMUM_REQUIRED(VERSION 3.9)
SET(CMAKE_SYSTEM_NAME Generic)
#SET(CMAKE_SYSTEM_PROCESSOR arm)
SET(CMAKE_CROSSCOMPILING TRUE)

# force compiler settings
SET(CMAKE_C_COMPILER_WORKS TRUE)
SET(CMAKE_CXX_COMPILER_WORKS TRUE)

# force cmake compilers
SET(CMAKE_ASM_COMPILER    "arm-none-eabi-gcc")
SET(CMAKE_C_COMPILER      "arm-none-eabi-gcc")
SET(CMAKE_CXX_COMPILER    "arm-none-eabi-g++")
SET(ELF2BIN               "arm-none-eabi-objcopy")


# if the environment does not specify build type, set to Debug
IF(NOT CMAKE_BUILD_TYPE)
  set(CMAKE_BUILD_TYPE "Debug"
        CACHE STRING "Choose the type of build, options are: Debug Release RelWithDebInfo MinSizeRel."
        FORCE)
ENDIF()

I have a weird bug that only happens when I start clion from the icon. Clicking on the icon I get: ImportError: No module named catkin.environment_cache in the cmake window. When I start clion from the console like I usually do I don't get this error, I get no error at all. I assume it has something to do with the environment variables that are different depending on the way I start it. I checked jetbrains-clion.desktop and it launches the same binary with the same options I do when starting it from the command line.

Is there a way to set the same environment variables for a .desktop file, as if the command was run from a terminal?