Clion error during pretty printers setup error while executing python code

GDB debug formatters not working #3608

Environment

• Intellij-Rust plugin version: v0.2.95.2120-183
• Rust toolchain version: rustc 1.33.0 (2aa4c46cf 2019-02-28)
• IDE name and version: CLion 2018.3.4
• Operating system: Arch Linux 5.0.4

Problem description

When debugging with GDB, formatters for all non-primitive types seem to be non-functional. When using LLDB, the formatters seem to work properly.

GDB (System, v8.2.1):

LLDB (Bundled, v6.0.0):

The following message is printed to the console when using GDB, leading me to believe it’s an issue with my setup:

Steps to reproduce

In a new binary project, paste the following code and set a breakpoint on the println line, then debug it with GDB:

The text was updated successfully, but these errors were encountered:

Doing some deeper digging, I found this in the logs:

It seems that this issue is caused by the way CLion is packaged in the Arch Linux AUR: The package aur/clion includes the core CLion IDE, but not the bundled toolchains — I only have aur/clion and aur/clion-lldb installed, and am using the system binaries for GDB and other tools. This means the directory /opt/clion/bin/gdb/renderers doesn’t exist, which is likely the cause of the error in the logs.

After installing the clion-gdb package, the error is gone from the console/log and the values are better formatted, although still not quite as nicely as with LLDB:

@dmarcuse Thanks for reporting and investigating the issue!

As for comparing LLDB and GDB: now CLion with GDB (even for C++) can show either summary (size in case of Vec ) or children (elements in case of Vec ). It is a bug and I hope it will be fixed in the future.

Also, you are welcome to suggest the Rust types that our formatters currently don’t support via creating new issues for it!

Источник

GDB debug formatters not working #3608

Comments

dmarcuse commented Mar 27, 2019

Environment

• Intellij-Rust plugin version: v0.2.95.2120-183
• Rust toolchain version: rustc 1.33.0 (2aa4c46cf 2019-02-28)
• IDE name and version: CLion 2018.3.4
• Operating system: Arch Linux 5.0.4

Problem description

When debugging with GDB, formatters for all non-primitive types seem to be non-functional. When using LLDB, the formatters seem to work properly.

GDB (System, v8.2.1):

LLDB (Bundled, v6.0.0):

The following message is printed to the console when using GDB, leading me to believe it’s an issue with my setup:

Steps to reproduce

In a new binary project, paste the following code and set a breakpoint on the println line, then debug it with GDB:

The text was updated successfully, but these errors were encountered:

dmarcuse commented Mar 27, 2019

Doing some deeper digging, I found this in the logs:

It seems that this issue is caused by the way CLion is packaged in the Arch Linux AUR: The package aur/clion includes the core CLion IDE, but not the bundled toolchains — I only have aur/clion and aur/clion-lldb installed, and am using the system binaries for GDB and other tools. This means the directory /opt/clion/bin/gdb/renderers doesn’t exist, which is likely the cause of the error in the logs.

dmarcuse commented Mar 27, 2019

After installing the clion-gdb package, the error is gone from the console/log and the values are better formatted, although still not quite as nicely as with LLDB:

ortem commented Mar 27, 2019 •

@dmarcuse Thanks for reporting and investigating the issue!

As for comparing LLDB and GDB: now CLion with GDB (even for C++) can show either summary (size in case of Vec ) or children (elements in case of Vec ). It is a bug and I hope it will be fixed in the future.

Also, you are welcome to suggest the Rust types that our formatters currently don’t support via creating new issues for it!

Источник

Clion hesitate this error, when start to debug the program. #22

Comments

sofair commented Jan 14, 2018

Platform: Windows Server 2008R2
Clion Version: 2017.3.1
Plugin Version: 2017.3.4

The text was updated successfully, but these errors were encountered:

satamas commented Jan 14, 2018

Have you tried to debug c/c++ with CLion on this machine?
Why I’m asking: we’ve put pretty printers file to our plugin, but in fact this is a copy of pretty printers file from CLion with important fix for Fortran. So I think, that you will face the same error if you will try to debug c/c++.

satamas commented Jan 14, 2018

In fact we don’t even need c/c++ code. Can you just try to debug your program with default Run Configuration, not ours and see what will happen, will the error be printed, or not.

sofair commented Jan 16, 2018

Hi satamas, I debuged a hello_world c code with default configuration. It does not output any error message. I also tryed debug hello fortran code with default configuration, it also does not hesitate any error message(did not pause at break points). But, debug with new fortran configuration, the reported error message came again.

satamas commented Jan 18, 2018

I’ve found problem, will fix it today

satamas commented Jan 18, 2018

Fixed in all branches.

qiujiangkun commented Oct 22, 2020

It still happens in my machine

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

GDB debug formatters not working #3608

Comments

dmarcuse commented Mar 27, 2019

Environment

• Intellij-Rust plugin version: v0.2.95.2120-183
• Rust toolchain version: rustc 1.33.0 (2aa4c46cf 2019-02-28)
• IDE name and version: CLion 2018.3.4
• Operating system: Arch Linux 5.0.4

Problem description

When debugging with GDB, formatters for all non-primitive types seem to be non-functional. When using LLDB, the formatters seem to work properly.

GDB (System, v8.2.1):

LLDB (Bundled, v6.0.0):

The following message is printed to the console when using GDB, leading me to believe it’s an issue with my setup:

Steps to reproduce

In a new binary project, paste the following code and set a breakpoint on the println line, then debug it with GDB:

The text was updated successfully, but these errors were encountered:

dmarcuse commented Mar 27, 2019

Doing some deeper digging, I found this in the logs:

It seems that this issue is caused by the way CLion is packaged in the Arch Linux AUR: The package aur/clion includes the core CLion IDE, but not the bundled toolchains — I only have aur/clion and aur/clion-lldb installed, and am using the system binaries for GDB and other tools. This means the directory /opt/clion/bin/gdb/renderers doesn’t exist, which is likely the cause of the error in the logs.

dmarcuse commented Mar 27, 2019

After installing the clion-gdb package, the error is gone from the console/log and the values are better formatted, although still not quite as nicely as with LLDB:

ortem commented Mar 27, 2019 •

@dmarcuse Thanks for reporting and investigating the issue!

As for comparing LLDB and GDB: now CLion with GDB (even for C++) can show either summary (size in case of Vec ) or children (elements in case of Vec ). It is a bug and I hope it will be fixed in the future.

Also, you are welcome to suggest the Rust types that our formatters currently don’t support via creating new issues for it!

Источник

CodeLite IDE

Python error while starting GDB session

Python error while starting GDB session

Post by caibbor » Sun Nov 12, 2017 12:23 am

Worked fine in Codelite 10. I moved to 11.0.4 today and found this problem, and then tried the latest git version today as well. Same problem in git/11.0.5

I’m not sure this is a bug, but it’s beginning to smell like it.

here’s full debug output:

60k line game engine. I’ve been putting codelite to the test

Re: Python error while starting GDB session

Post by eranif » Sun Nov 12, 2017 1:01 am

Re: Python error while starting GDB session

Post by caibbor » Sun Nov 12, 2017 2:57 am

Re: Python error while starting GDB session

Post by eranif » Sun Nov 12, 2017 10:00 am

Re: Python error while starting GDB session

Post by caibbor » Sun Nov 12, 2017 8:48 pm

which shouldn’t be happening because that library is placed in a local directory in my project, and the directory is added to the linker settings for library path. This all works in the older version of codelite as mentioned.

I suspect codelite is ignoring my library include paths in Project Settings -> Linker -> Library Search Path. That setting is as follows (it’s a 32bit program):

Re: Python error while starting GDB session

Post by eranif » Sun Nov 12, 2017 9:56 pm

The settings in the linker are used for *link* time not runtime
You should add them to the LD_LIBRARY_PATH before launching the debugger.

Nothing changed in this regard bettween CodeLite 11 and 9 (I would even say CodeLite 6. )
If I had to guess, I would say that something was changed in your environment

Try setting the proper LD_LIBRARY_PATH in a terminal and then launch CodeLite, or update the LD_LIBRARY_PATH in settings->environment variables

Источник

Improve WSL support about clion-embedded-arm HOT 3 CLOSED

Comments (3)

Try to manually set the binary file path in the run configuration.

invertium commented on January 13, 2023

I’m having the same issue. I tried changing the ‘exectuable’ path directly over the windows path which didnt change anything.
Fixed by the openOCD GDB settings from ‘shipped with clion’ to ‘from toolchain’ and changing the debugger in the toolchain setting like I would for MacOS

elmot commented on January 13, 2023

Related Issues (20)

• Show memory statistics after compilation HOT 1
• Unable to debug if linker script has two applications HOT 2
• How to use gprof HOT 2
• Document how to switch to a C++ Project HOT 2
• Cannot load settings from file workspace.xml HOT 4
• Out-of-source CMake builds differ from CLion HOT 12
• How do you develop this plugin? HOT 1
• OpenOCD support dialog incomplete. No way of specifying board HOT 2
• Would be possible to add MCU Registers view window/perspective during debugging?
• Error when updating CMake Project. Configuration problem HOT 1
• Load Project Setting Error after add OpenOCD configuration HOT 4
• Wrong objcopy executed. HOT 1
• ConfigurationException: Please open settings dialog and fix OpenOCD home HOT 1
• Debug fails with «Error running ‘OCD test-program’: Debugger executable is incorrect» HOT 2
• Does STLink V2 support now? HOT 1
• Set board config file from CMake HOT 2
• Support multiple config file HOT 2
• Feature request: relative paths for openocd board config HOT 2
• Warn : no flash bank found for address 0x00000000

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

Laravel

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Источник

Незаметно для меня прилетело обновление на Clion. Теперь у меня версия 2020.3. После этого обновления происходит ошибка GDB при его запуске

Error during pretty printers setup: Error while executing Python code.

Some features and performance optimizations will not be available.

После этого я увидел, что значения переменных в принципе перестали выводится.
Искал ответы тут и тут, но ничего не помогло. Использую minGW. Переустанавливать пробовал, как Clion, так и minGW. Clion устанавливался через toolbox. Если смотреть ошибку, представленную здесь, то вот мои фрагменты

WARN - brains.cidr.execution.debugger - >python import sys; sys.dont_write_bytecode = True; sys.path.insert(0, "C:/Users/matve/AppData/Local/JetBrains/Toolbox/apps/CLion/ch-0/203.5981.166/bin/gdb/renderers"); from default.printers import register_default_printers; register_default_printers(None); from default.libstdcxx_printers import patch_libstdcxx_printers_module; patch_libstdcxx_printers_module();  
WARN - brains.cidr.execution.debugger - <^error,msg="Error while executing Python code." 
WARN - brains.cidr.execution.debugger - Error during pretty printers setup: Error while executing Python code.

Таких предупреждений у меня много, но они все однотипные

Незаметно для меня прилетело обновление на Clion. Теперь у меня версия 2020.3. После этого обновления происходит ошибка GDB при его запуске

Error during pretty printers setup: Error while executing Python code.

Some features and performance optimizations will not be available.

После этого я увидел, что значения переменных в принципе перестали выводится.
Искал ответы тут и тут, но ничего не помогло. Использую minGW. Переустанавливать пробовал, как Clion, так и minGW. Clion устанавливался через toolbox. Если смотреть ошибку, представленную здесь, то вот мои фрагменты

WARN - brains.cidr.execution.debugger - >python import sys; sys.dont_write_bytecode = True; sys.path.insert(0, "C:/Users/matve/AppData/Local/JetBrains/Toolbox/apps/CLion/ch-0/203.5981.166/bin/gdb/renderers"); from default.printers import register_default_printers; register_default_printers(None); from default.libstdcxx_printers import patch_libstdcxx_printers_module; patch_libstdcxx_printers_module();  
WARN - brains.cidr.execution.debugger - <^error,msg="Error while executing Python code." 
WARN - brains.cidr.execution.debugger - Error during pretty printers setup: Error while executing Python code.

Таких предупреждений у меня много, но они все однотипные