clion plugin - unable to specify GDB

[asa]

I am unable to setup a debugger with the clion plugin. I get an error in the console: Error running Bazel run my_project:example: GDB executable not specified

I have tried to use --run_under, as well as setup gdb remote debugger, with no luck.
Perhaps I just need better docs?

[brendandouglas]

Hi @asa, you can specify the GDB binary in Settings > Build, Execution, Deployment > Toolchains.

[brendandouglas]

I'll close this -- please reopen if that didn't fix it.

[asa]

I believe the problem is that I am running on OSX. The debugger is not found. Perhaps its assuming GDB?

…

On Tue, Jan 24, 2017 at 1:43 PM, brendandouglas ***@***.***> wrote: Closed #46 <#46>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAF3mQETb3mUvUzBYB0kRfM2t429btAlks5rVnB3gaJpZM4LsmEA> .

[brendandouglas]

We currently only support linux. We have support for OSX and Windows planned at some stage, but it's not a current priority. Some things may work on OSX (and do indeed seem to, based on some of the comments here), but it's completely untested.

As a separate issue, CLwB currently only supports gdb (see BlazeCidrLauncher for the relevant code). Still, if you have gdb installed on your system, and specify the binary path in the settings, I'd expect this to work.

[david-german-tri]

@asa, you may be interested in bazelbuild/bazel#2537. With the workarounds I've described on that thread, I've been able to generate dSYM files in bazel-bin. Separately, I was able to specify "Bundled GDB 7.11.1" in the CLion 2016.2.2 settings. I could then debug Bazel-built binaries using GDB, in CLion, on OS X.

One additional caveat: if your breakpoints don't take effect, check the console. GDB may be complaining that it can't find your source files, which can be worked around by adding set directories /path/to/my/workspace/root to your .gdbinit. This is not a CLion-specific problem, although CLion triggers it by passing absolute paths to GDB. Those paths appear invalid to GDB on OS X, for reasons I haven't fully worked out. It probably has something to do with the paths that the Bazel build embeds in DWARF symbols.