[all-commits] [llvm/llvm-project] b57c32: [lldb][Windows] Append access-violation detail to ...

[Charles Zablit via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b57c32db810bb8619220591224b4a71bc2d4b40d
      https://github.com/llvm/llvm-project/commit/b57c32db810bb8619220591224b4a71bc2d4b40d
  Author: Charles Zablit <c_zablit at apple.com>
  Date:   2026-06-11 (Thu, 11 Jun 2026)

  Changed paths:
    M lldb/source/Plugins/Process/Windows/Common/CMakeLists.txt
    A lldb/source/Plugins/Process/Windows/Common/ExceptionRecord.cpp
    M lldb/source/Plugins/Process/Windows/Common/ExceptionRecord.h
    M lldb/source/Plugins/Process/Windows/Common/NativeProcessWindows.cpp
    M lldb/source/Plugins/Process/Windows/Common/ProcessDebugger.cpp
    M lldb/source/Plugins/Process/Windows/Common/ProcessWindows.cpp

  Log Message:
  -----------
  [lldb][Windows] Append access-violation detail to lldb-server stop description (#203301)

`lldb-server.exe` reports access violations with only the bare exception
code (e.g. `Exception 0xc0000005 encountered at address 0x...`), while
the in-process Windows debugger produces the much more useful `Access
violation
  reading location 0x...` / `writing` / `DEP at` form.

This patch lifts the in process helper into a method of the
`ExceptionRecord` class to allow both Windows plugins to use it.

This fixes `exception_access_violation.cpp` with
`LLDB_USE_LLDB_SERVER=1`.

rdar://179366768



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications