leftmachines.blogg.se - Clion debugger not working

Clion debugger not working for mac#
Clion debugger not working Patch#
Clion debugger not working code#
Clion debugger not working license#

Clion debugger not working code#

So you should be able to navigating in the code base, e.g.

If all go well, your CLion/IntelliJ will still have some errors but they can build index successfully.

It's recommended that making dedicated Impala dir for them.

There're some conflicts for CLion and IntelliJ to work in the same folder, e.g.

Applications/CLion.app/Contents/MacOS/clion # or /Applications/IntelliJ\ IDEA.app/Contents/MacOS/idea Then source $IMPALA_HOME/bin/impala-config.sh and launch CLion/IntelliJ in your terminal.

Clion debugger not working Patch#

The patch comments out the dependency of LLVM (TODO: resolve this in IMPALA-8229) and fix some stale versions and java paths.

Apply this patch in your MacOS env: dev_env_for_Mac.patch (Command: git apply $somewhere/dev_env_for_Mac.patch).

But be aware of those compilation outputs and cmake cache files. Now the contents of $IMPALA_HOME in your MacOS laptop should be the same as your Ubuntu environment.

Transfer those tar files back to your MacOS laptop and unpack them in your $IMPALA_HOME.

(Transferring lots of small files between file systems will be time consuming)

After you compile Impala successfully in your Ubuntu environment, package these folders in $IMPALA_HOME: be/generated-sources, fe/generated-sources, toolchain.

If you don't have a Ubuntu machine, you can compile Impala in Docker. If you have a Ubuntu machine, go and compile Impala in it first ( link). However, you can still use IntelliJ and CLion on Mac for coding as long as you have compiled Impala successfully in a Ubuntu environment.

Clion debugger not working for mac#

there are no pre-built toolchain for Mac and the toolchain may not be compilable on Mac. You may encounter many problems in MacOS, i.e. The above content requires that you can bootstrap your system successfully. You can use the ClangFormatIJ plugin to run clang-format in IntelliJ and CLion WIP: Using IntelliJ and CLion on Mac Setting break point and debug Using clang-format in IntelliJ and CLion Copy PYTHONPATH and paste it to Environment Variables in Run/Debug Configurationsĥ. Need to set Environment Variables like what $IMPALA_HOME/bin/impala-python did:ġ. bash -x $IMPALA_HOME/bin/impala-pythonĢ.

Go to Run -> Attach to Local Processes.

Select the python interpreter in $IMPALA_HOME/infra/python/env/bin/python.

Add an existing virtual env environment.

Go to Build, Execution, Deployment -> Python Interpreter.

Impala Shell Development using CLion Setup If you see an error "ptrace: Operation not permitted" then follow the instructions here to allow ptracing of non-child processes.

Add catalog-debug configuration to debug catalog with a port number of 30030.

Add impalad-debug configuration to debug impalad with a port number of 30000.

Add LD_LIBRARY_PATH with the value of $IMPALA_HOME/be/build/latest/service.

To be able to attach to a local process, follow the instruction here.įront-end Development using IntelliJ Setup.

Always source $IMPALA_HOME/bin/impala-config.sh prior to launching IntelliJ or CLion.

Bootstrap the system for Impala development.

Clion debugger not working license#

You can request for an open source license for CLion. It is value and it is shown correctly as you can see on the screenshot. Second attribute of tree class is comparator and that is not a pointer. It is class tree and it contains pointer to object of class node. But I do not know how could be used other than 4.8.4, because in my /usr/bin is just version 4.8.4.ĭebugger shows correctly elements in vector and entire vector, but object of my custom class, which contains objects of my another custom class is not shown correctly. But I have no idea, where to find, what version of g++ is used for debugging.

Maybe this could be problem, except I am using g++, not gcc. "In my case, I built my project with GCC-4.8 and tried to debug with GCC-4.6. In the link I wrote in the first post is something like this:

Maybe, if it could compile with gcc -gdwarf could help. It looks like there is not -lstdc++, but it is.

Then I got so much errors in building process. I tried to change this to GCC, and added this flag: "-lstdc++" Ok, so, now I now I am using g++ 4.8.4 version.