Since lldb 19 syntax highlight is missing on Mac OS

[glepnir]

after upgrade to lldb 19 the syntax highlight of output in lldb is missing back to 18 works well. thanks.

[DavidSpickett]

We'll need some more details:

• Which platform are you using LLDB on? (Linux / Mac / Windows)
• Which version of 18 are you using? (I assume 19 is the recent 19.1.0)
• Where did you install those copies of lldb from? (apt, homebrew, built them yourself)
• Which source language are you using that's missing the highlighting?
• If it's not source display, which commands are now missing highlighting?

I remember some change around detecting whether colours are supported by the terminal. I might be able to find that if you can provide those details first.

[llvmbot]

@llvm/issue-subscribers-lldb

Author: None (glepnir)

after upgrade to lldb 19 the syntax highlight of output in lldb is missing back to 18 works well. thanks.

[glepnir]

• Which platform are you using LLDB on? Macos 15.0 with M3 pro chip
• Which version of 18 are you using? lldb version 19.1.0 Not work. lldb-1600.0.36.3 / lldb 18 works well
• Where did you install those copies? brew
• Which source program language? C/C++
• Which commands? b set point then do trigger it and input n

[DavidSpickett]

I don't have a Mac to test this but I'm pretty sure it's due to 6bf450c / #92865.

On Linux I still get colour by default:

However I think this is because the ncurses on my system includes a copy of (or depends on) terminfo without lldb's build having to add it explicitly. So I get the features of terminfo via ncurses. We've had other issues with that patch along these lines, though usually it's refusing to build at all.

$ ldd ./bin/lldb | grep -v LLVM | grep -v clang
<...>
        libncurses.so.6 => /lib/aarch64-linux-gnu/libncurses.so.6 (0x0000ffffb07a0000)
        libtinfo.so.6 => /lib/aarch64-linux-gnu/libtinfo.so.6 (0x0000ffffb0750000)
<...>

The advice on that commit is:
"Remove it to reduce the closure size and improve portability of LLVM-based tools. Users can still use command line arguments to toggle color support expliticly."

Which you do with a setting, here I'm disabling it but use true to enable it instead:

If the Apple produced builds of LLDB don't have this problem, then it feels like Homebrew may need to adjust their recipe. Perhaps Homebrew builds are using their own ncurses/terminfo. In some sense this is "working as intended" but Linux doesn't need to change the setting to I think there's probably a way to fix the build configuration.

@JDevlieghere could you see if your internal builds of LLDB have this problem?

@glepnir if you have the time and/or enthusiasm you could rebuild lldb with the linked patch reverted and see if that fixes the problem. Try to get Homebrew to do it though, so you link to the same libraries as it does. Though even if that does fix this for you, the chances of an upstream revert seem low.

[DavidSpickett]

You can also add settings set use-color true to your ~/.lldbinit file, so that you don't have to do it in every new session.

[glepnir]

use otool -L for check ..no ncurses dylib

/opt/homebrew/opt/llvm/bin/lldb:
        @rpath/liblldb.19.1.0.dylib (compatibility version 0.0.0, current version 19.1.0)
        @rpath/libclang-cpp.dylib (compatibility version 0.0.0, current version 0.0.0)
        @rpath/libLLVM.dylib (compatibility version 1.0.0, current version 19.1.0)
        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1800.101.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1351.0.0)

settings set use-color true this works . 3q