[all-commits] [llvm/llvm-project] 96000f: [lldb] Simplify SBCommandInterpreter::SourceInitFi...

Pavel Labath via All-commits all-commits at lists.llvm.org
Wed Feb 9 07:18:50 PST 2022


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 96000f5c2bf99365bb45528898c864fcb1c7780b
      https://github.com/llvm/llvm-project/commit/96000f5c2bf99365bb45528898c864fcb1c7780b
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2022-02-09 (Wed, 09 Feb 2022)

  Changed paths:
    M lldb/include/lldb/Interpreter/CommandInterpreter.h
    M lldb/source/API/SBCommandInterpreter.cpp

  Log Message:
  -----------
  [lldb] Simplify SBCommandInterpreter::SourceInitFileInHomeDirectory

just have it delegate to the new overload.


  Commit: 9611282c64f4cec1d6d0d997202762fa38e99663
      https://github.com/llvm/llvm-project/commit/9611282c64f4cec1d6d0d997202762fa38e99663
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2022-02-09 (Wed, 09 Feb 2022)

  Changed paths:
    M lldb/test/API/tools/lldb-server/main.cpp

  Log Message:
  -----------
  [lldb] Stabilize threaded windows lldb-server tests

The tests enabled in 9e699595 are not passing reliably -- sometimes they
report seeing fewer threads than expected.

Based on my (limited) research, this is not a lldb bug, but simply a
consequence of the operating system reporting their presence
asynchronously -- they're reported when they are scheduled to run (or
something similar), and not at the time of the CreateThread call.

To fix this, I add some additional synchronization to the test inferior,
which makes sure that the created thread is alive before continuing to
do other things.


Compare: https://github.com/llvm/llvm-project/compare/370ea1a19928...9611282c64f4


More information about the All-commits mailing list