[all-commits] [llvm/llvm-project] bd586d: [lldb] Use the standard GDB remote thread for a no...

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: bd586dd26e3ba49616175c14cb2970c581fb94b7
      https://github.com/llvm/llvm-project/commit/bd586dd26e3ba49616175c14cb2970c581fb94b7
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-08-06 (Thu, 06 Aug 2026)

  Changed paths:
    M lldb/source/Plugins/Process/wasm/ProcessWasm.cpp
    M lldb/source/Plugins/Process/wasm/ThreadWasm.cpp
    M lldb/test/API/functionalities/gdb_remote_client/TestWasm.py

  Log Message:
  -----------
  [lldb] Use the standard GDB remote thread for a non-Wasm process (#214380)

CanDebug returns true whenever the plugin is requested by name, and the
architecture is not known until the stub reports it after connecting.
This means that a non-Wasm process can end up with a ThreadWasm whose
register context and unwinder have nothing to operate on.

Create the plain ThreadGDBRemote once the architecture is known, and add
a helper so that the check covers wasm64 as well as wasm32.

rdar://182229301



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