Displaying 3 results from an estimated 3 matches for "__zn4llvm9stringrefc1epkc".
2018 Dec 15
4
Disabling LLVM_ATTRIBUTE_ALWAYS_INLINE for development?
...o debug LLVM libraries can be super
frustrating, because a lot of LLVM classes, like the constructor for
StringRef, are marked LLVM_ATTRIBUTE_ALWAYS_INLINE. So when I attempt
to have lldb evaluate an expression that implicitly instantiates a
StringRef, I get 'error: Couldn't lookup symbols:
__ZN4llvm9StringRefC1EPKc'.
As an example, most recently this happened to me when playing around
with llvm::AttributeSet, having attached lldb to an opt built with
-DCMAKE_BUILD_TYPE="Debug":
(lldb) e $AS.hasAttribute("myattr")
error: Couldn't lookup symbols:
__ZN4llvm9StringRefC1EPK...
2018 Dec 16
3
Disabling LLVM_ATTRIBUTE_ALWAYS_INLINE for development?
...trating, because a lot of LLVM classes, like the constructor for
> > StringRef, are marked LLVM_ATTRIBUTE_ALWAYS_INLINE. So when I attempt
> > to have lldb evaluate an expression that implicitly instantiates a
> > StringRef, I get 'error: Couldn't lookup symbols:
> > __ZN4llvm9StringRefC1EPKc'.
> >
> > As an example, most recently this happened to me when playing around
> > with llvm::AttributeSet, having attached lldb to an opt built with
> > -DCMAKE_BUILD_TYPE="Debug":
> >
> > (lldb) e $AS.hasAttribute("myattr")
> >...
2018 Dec 17
2
Disabling LLVM_ATTRIBUTE_ALWAYS_INLINE for development?
...es, like the constructor for
>> > > StringRef, are marked LLVM_ATTRIBUTE_ALWAYS_INLINE. So when I attempt
>> > > to have lldb evaluate an expression that implicitly instantiates a
>> > > StringRef, I get 'error: Couldn't lookup symbols:
>> > > __ZN4llvm9StringRefC1EPKc'.
>> > >
>> > > As an example, most recently this happened to me when playing around
>> > > with llvm::AttributeSet, having attached lldb to an opt built with
>> > > -DCMAKE_BUILD_TYPE="Debug":
>> > >
>> > > (ll...