Ok that was it, it was because my type was called Class. Oops!
On Fri, Oct 26, 2018 at 4:28 PM Jim Ingham wrote:
> Most C++ classes and C structs don't have data formatters, particularly
> not classes that you write yourself.
>
> The way value printing works in lldb is that we start by making the
Most C++ classes and C structs don't have data formatters, particularly not
classes that you write yourself.
The way value printing works in lldb is that we start by making the ValueObject
for the value from its Type, so at that stage it is just a direct view of the
members of the object. Th
So, the second command works, but the first one doesn't. It doesn't give
any error, but on the other hand, it doesn't change the results of printing
the variable. When I run type category list though, I get this:
(lldb) type category list
Category: default (enabled)
Category: VectorTypes (enable
https://bugs.llvm.org/show_bug.cgi?id=39459
Frederic Riss changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |syaghm...@gmail.com
CC|
https://bugs.llvm.org/show_bug.cgi?id=39459
Bug ID: 39459
Summary: Enum class variables can't be used as function
arguments
Product: lldb
Version: unspecified
Hardware: All
OS: All
Status: NEW
Remove the "not"...
Jim
> On Oct 26, 2018, at 10:24 AM, Jim Ingham wrote:
>
> But at the minimum, not loading formatters for a language that we can
> determine isn't used in this program seems like something we should try to
> avoid.
___
lldb-dev m
The data formatters don't currently have a specified language. We should
maybe add that and then we could only load formatters for a language when its
runtime gets loaded. Then they could also know to turn themselves on and off
based on the language of the current frame, or of the current exp
On 26 Oct 2018, at 16:25, Kristof Beyls via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
On 26 Oct 2018, at 04:26, Richard Smith
mailto:rich...@metafoo.co.uk>> wrote:
On Thu, 25 Oct 2018 at 05:10, Kristof Beyls via cfe-dev
mailto:cfe-...@lists.llvm.org>> wrote:
On 5 Oct 2018, at 07:04,
As an llvm-bugs subscriber, I would prefer *not* to have email for every
comment to every bug. That's what the CC list is for.
If the admins guarantee that there is at least one auto-cc (who promises to pay
attention) for each component, I think that is sufficient.
Also +1 for UNCONFIRMED.
--pa
On 26 Oct 2018, at 04:26, Richard Smith
mailto:rich...@metafoo.co.uk>> wrote:
On Thu, 25 Oct 2018 at 05:10, Kristof Beyls via cfe-dev
mailto:cfe-...@lists.llvm.org>> wrote:
On 5 Oct 2018, at 07:04, Dean Michael Berris
mailto:dean.ber...@gmail.com>> wrote:
Thank you for starting this conversa
Note that I also tried this with a a linux / DWARF executable and had the
same result.
On Fri, Oct 26, 2018 at 3:21 AM Zachary Turner wrote:
> Hello,
>
> I've got this code:
>
> class Class {
> int x = 0;
> short y = 1;
> char z = 'z';
> } C;
>
> int main(int argc, char **argv) {
> __deb
Hello,
I've got this code:
class Class {
int x = 0;
short y = 1;
char z = 'z';
} C;
int main(int argc, char **argv) {
__debugbreak();
return 0;
}
and I run the following LLDB session:
lldb.exe -f foo.exe
(lldb) target create "foo.exe"
Current executable set to 'foo.exe' (x86_64).
(ll
12 matches
Mail list logo
