This doesn't prevent breakpoints, but it seems to prevent inspecting
local variables. Running "bt full" in gdb says "no locals" for every
stack frame in LLVM or Clang libraries.
By the way, this bug seems to be related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413646
--
Nicolás
Control: severity -1 minor
(Found while investigating #852746 - these are the only two places in LLVM with
that error message,
Oops - there are actually three and #852746 is the other one. Sorry for noise.
Control: severity -1 normal
Looks like this isn't just warnings - it also prevents breakpoints
working in the affected files.
(Found while investigating #852746 - these are the only two places in
LLVM with that error message,
Le 14/01/2017 à 14:53, Rebecca N. Palmer a écrit :
> It happens every time I run something that uses it in gdb, including LLVM's
> own executables; do you mean it doesn't for you?
I was talking about a potential fix :)
It happens every time I run something that uses it in gdb, including
LLVM's own executables; do you mean it doesn't for you?
$ sudo apt-get install gdb libllvm3.9-dbg llvm-3.9
$ gdb llvm-link-3.9
[...]
(gdb) run
Starting program: /usr/bin/llvm-link-3.9
warning: Could not find DWO CU
Le 14/01/2017 à 13:46, Rebecca N. Palmer a écrit :
> warning: Could not find DWO CU
> CMakeFiles/LLVMSupport.dir/APFloat.cpp.dwo(0x7c87b0db7d3d4058) referenced by
> CU at offset 0x0 [in module
> /usr/lib/debug/.build-id/ba/46ea8b237c3239edf83c2033c3cd7ab15c0452.debug]
Doesnt ring a bell to me.
Package: libllvm3.9-dbg
Version: 1:3.9.1-2
Severity: minor
This -dbg package produces enough warnings that backtraces become
difficult to read:
$ sudo apt-get install beignet-opencl-icd beignet-dev libllvm3.9-dbg
$ OCL_STRICT_CONFORMANCE=0 gdb --args /usr/lib/x*/beignet/utest_run -c
7 matches
Mail list logo
