Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CLion and Rust debugging issue

See original GitHub issue

This is a CLion and Rust debugging issue.

When a debug point is set on a library (dependency crate), the debugger doesn’t while running in debug mode.

Environment

IntelliJ Rust plugin version: 0.2.106.2135-192
Rust toolchain version:

$rustc -V
rustc 1.38.0-nightly (6e310f2ab 2019-07-07)

$rustup -V
rustup 1.19.0 (2af131cf9 2019-09-08)

IDE name and version: CLion 2019.2.3

Build #CL-192.6817.18, built on September 24, 2019
Runtime version: 11.0.4+10-b304.69 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: ParNew, ConcurrentMarkSweep
Memory: 1987M
Cores: 12
Registry: run.processes.with.pty=TRUE
Non-Bundled Plugins: com.vladsch.idea.multimarkdown, org.toml.lang, org.rust.lang

Operating system:

Mac OS Majave
Version 10.14.6 (18G103)

Problem description

Debugger doesn’t stop in break-points set in dependency crates defined in Cargo.toml

Steps to reproduce

Issue Analytics

State:
Created 4 years ago
Reactions:6
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

hronrocommented, Nov 2, 2019

Hi all, I finally fixed this by uninstall the latest CLion 2019.2.5 and installed CLion 2019.2.1, it seems this bug only happens with the latest CLion version.

PS: I also tried delete CLion config files in ~/Library/Preferences, or reinstall CLion 2019.2.5, none of them works.

0reactions

hronrocommented, Nov 2, 2019

I don’t have any anti-virus softwares in my mac