WSL+Valgrind+Clion

Make a note of WSL Tool chain to use valgrind The process of

There is no target on the network clion stay windows Next use valgrind Chinese course of ,jetbrains The official tutorial is also vague , Write down the whole process and reference web tutorial here ,woc After writing, I found that there was a tutorial https://blog.csdn.net/u010606602/article/details/80782650.

install WSL As valgrind The bridge of , Make in windows It can also run under the weather valgrind etc. linux Exclusive tools .

1. First, modify the image source , This is relatively simple and it varies according to the system , The general path is first cp preservation /etc/apt/sources.list, Then delete all contents and manually add domestic sources, After adding, use
   sudo apt-get update;sudo apt-get upgrade;sudo apt-get install build-essential. If there is a problem with the third command , Then it should be dependence broken The problem of , It is recommended to refit directly wsl. After installing the basic environment, you need to install it manually valgrind and cmake Tools , The former is direct sudo apt-get that will do , The latter may require source code installation （https://www.linuxidc.com/Linux/2018-09/154165.htm）.
2. Then you can open it clion, stay Setting->Build,Execution,Deployment->Toolchains Create a new one in WSL Type of tool chain , Will automatically import Environment, however Credentials Manual setting required , This needs to be wsl Open ahead of time ssh, reference https://www.cnblogs.com/mydailycoding/p/12375273.html, Successful connection will show Connected.
   3. This is an official process , But I didn't find the video sh Script source , So I just referred to his ideas , But he didn't follow his practice ：evget.com/video/2616
   4. Now it's finished wsl Configuration and installation of environment , But there are problems ：
      • Direct operation valgrind Will be displayed cound not found executable valgrind, You need to add the path manually , Directly find the subsystem in windows Add the root directory under C:\Users\ user name \AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs\usr\bin
      • If installed boost library , So use wsl As a tool chain, he can't find it , Can be in cmakelists.txt The dependent library is directly referenced in the file （ Thanks to the wsl Medium /mnt Catalog ）include_directories(/mnt/e/boost_1_73_0) Locate the windows Under the system boost Library file is good .