[all-commits] [llvm/llvm-project] c941be: [lldb] Fix qEcho message handling. (#145675)

[eleviant via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: c941bee75d252ac9a9787dd0594959d890ddb073
      https://github.com/llvm/llvm-project/commit/c941bee75d252ac9a9787dd0594959d890ddb073
  Author: eleviant <56861949+eleviant at users.noreply.github.com>
  Date:   2025-06-25 (Wed, 25 Jun 2025)

  Changed paths:
    M lldb/packages/Python/lldbsuite/test/gdbclientutils.py
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.h
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
    M lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
    M lldb/test/API/commands/command/script_alias/TestCommandScriptAlias.py
    M lldb/test/API/functionalities/gdb_remote_client/TestGDBRemoteClient.py

  Log Message:
  -----------
  [lldb] Fix qEcho message handling. (#145675)

This fixes issues found in e066f35c6981c720e3a7e5883efc40c861b3b7, which
was later reverted. The problem was with "k" message which was sent with
sync_on_timeout flag set to true, so lldb was waiting for response,
which is currently not being sent by lldb-server. Not waiting for
response at all seems to be not a solution, because on MAC OS X lldb
waits for response from "k" to gracefully kill inferior.



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