macOS (arm64) Watch window variables, cannot display in hex

[mrfirmware]

I'm using macOS Monterey with lldb on a local command line application written in C, -std=c11. Debugging works great. However, I cannot add a variable to the display window with the hex suffix, e.g. foo works and displays foo but foo, x does not work. Instead I see

Error: Unrecognized format of field "value" in result: result-class: done

If I click on it a bit the line changes to

changelist: [{name=var127,value=0,in_scope=true,type_changed=false, type_changed=0}]

Is the ,x format specifier supposed to work? What am I doing wrong?

[vadimcn]

That doesn't look like any error I know. Are you sure you are using the CodeLLDB extension?

[mrfirmware]

Pretty sure? I have the extension loaded. Here's my launch.json entry:

        {
            "name": "(lldb) Launch [recycle]",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build_artifacts/foo",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${fileDirname}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "lldb"
        }

Now I see that "type" should be "lldb". After changing "cppdbg" to "lldb" the type specifier is working. But not for the fields within the aggregate types. Oh well.

[vadimcn]

But not for the fields within the aggregate types

They don't? Can you give an example?
Note that there's also a global formatting setting accessible via "Display Format..." command

[mrfirmware]

Maybe I don't understand how it's supposed to work but here I have two Foo's with the ,x specifier yet the elements are still shown in their native types. I don't think I want to see everything in hex but it's good to know there's a display format command. Thanks.

[vadimcn]

Format specifiers are intended to be used on scalars. For composite types, they affect summary display, but not children.
Why don't you watch foo.bitmask directly?

[mrfirmware]

What you say agrees with what I'm seeing. Thanks. I write firmware and I have to inspect many large structs that have addresses coded as uint64_t for some reason (not my doing). Also, sizes are sometimes easier to comprehend when in hex. Anyhow, I'd have to watch many many aggregate type elements so it's not so practical but I will try your suggestion where I can. Thank you.