macOS下LLDB调试CEF程序时std::string显示异常求助

It looks like you're hitting a common compatibility snag between CEF's bundled dependencies, older Clang versions, and LLDB's type formatting logic. Let's break down the likely causes and actionable fixes:

Possible Root Causes #

1. Mismatched Standard Library Versions #

CEF binaries typically ship with their own copy of libc++ (the LLVM C++ standard library). If your build links against CEF's bundled libc++ instead of the one paired with Brew's Clang 5.0.1, LLDB's default type formatters (which expect the Clang/LLVM libc++ memory layout) will fail to parse std::string correctly—resulting in the garbage output you're seeing.

2. Sanitizer-Altered Memory Layout #

Your compile flags include -fsanitize=leak -fsanitize=address. AddressSanitizer (ASAN) modifies the memory structure of standard library types like std::string to add instrumentation for leak/buffer overflow detection. Older LLDB versions (especially those paired with Clang 5.0.1) often lack formatters that account for ASAN's modified layouts, leading to broken display.

3. LLDB-Clang Version Incompatibility #

If you're using the system-provided LLDB instead of the one bundled with Brew's Clang 5.0.1, there's a high chance of version mismatch. LLDB relies on precise knowledge of the compiler's type layouts, so using a mismatched version will prevent it from correctly interpreting std::string.

Fixes to Try #

1. Use the Matching LLDB Binary #

Launch LLDB from the same Brew LLVM installation you used to compile your code—this ensures LLDB understands the type layout generated by your compiler:

/usr/local/opt/llvm/bin/lldb /path/to/your/ExecutionGraphGUI

2. Disable Sanitizers Temporarily #

Test if the issue resolves by removing -fsanitize=leak -fsanitize=address from your compile flags and rebuilding. If std::string displays correctly after this, the problem is ASAN's modified memory layout. For Clang 5.0.1, your options here are:

• Stick with sanitizers and use a custom formatter (see below)
• Upgrade to a newer Clang/LLVM version (15+ recommended) where LLDB has better ASAN type support.

3. Align CEF's libc++ Linking #

Check your CMake configuration to ensure you're linking against the same libc++ as your Clang installation, not CEF's bundled version. CEF's CMake modules often include options like CEF_USE_SYSTEM_LIBCXX (verify your CEF version's docs) to force using the system/Brew libc++.

4. Create a Custom LLDB Formatter for std::string #

If the above fixes don't work, you can manually define a formatter to parse the std::__1::string structure shown in your fr v -R t output. Save this as string_summary.py:

import lldb

def summarize_std_string(value, internal_dict):
    # Navigate to the __rep union inside the string
    rep = value.GetChildMemberWithName('__r_').GetChildMemberWithName('__value_')
    
    # Check for Small String Optimization (SSO)
    sso_size = rep.GetChildMemberWithName('__s').GetChildMemberWithName('__size_').GetValueAsUnsigned()
    if sso_size < 256:
        # Extract SSO data
        sso_data = rep.GetChildMemberWithName('__s').GetChildMemberWithName('__data_')
        return f'"{sso_data.GetSummary().strip("\"")}" (SSO, {sso_size} bytes)'
    else:
        # Extract heap-allocated string data
        long_data_ptr = rep.GetChildMemberWithName('__l').GetChildMemberWithName('__data_')
        long_size = rep.GetChildMemberWithName('__l').GetChildMemberWithName('__size_').GetValueAsUnsigned()
        # Read the actual string from memory
        error = lldb.SBError()
        string_data = long_data_ptr.GetPointeeData(0, long_size).GetString(error, 0)
        if error.Success():
            return f'"{string_data}" (heap, {long_size} bytes)'
        else:
            return f'Invalid string at {long_data_ptr} (size {long_size})'

# Register the formatter when the script is imported
def __lldb_init_module(debugger, internal_dict):
    debugger.HandleCommand('type summary add -F string_summary.summarize_std_string std::__1::string')

Then load the script in LLDB:

command script import /path/to/string_summary.py

Now fr v t should display the correct string content.

Bonus: Upgrade Clang/LLVM #

Clang 5.0.1 is quite old (released in 2017). Upgrading to a modern version (e.g., LLVM 15 or later) via Brew will resolve many compatibility issues with CEF, LLDB, and sanitizers, making debugging much smoother.

内容的提问来源于stack exchange，提问作者Gabriel