https://bugs.llvm.org/show_bug.cgi?id=49433

            Bug ID: 49433
           Summary: concurrent_events tests: wrong breakpoint hit with
                    multiple concurrent breakpoints
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev@lists.llvm.org
          Reporter: mgo...@gentoo.org
                CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

All of the tests involving multiple breakpoints suffer from randomly
establishing the wrong breakpoint hit count, e.g.:

FAIL: LLDB (/home/mgorny/llvm-project/build.arm64/bin/clang-aarch64) :: test
(TestConcurrentTwoBreakpointThreads.ConcurrentTwoBreakpointThreads)
======================================================================
FAIL: test (TestConcurrentTwoBreakpointThreads.ConcurrentTwoBreakpointThreads)
   Test two threads that trigger a breakpoint.
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py",
line 149, in wrapper
    return func(*args, **kwargs)
  File
"/home/mgorny/llvm-project/lldb/test/API/functionalities/thread/concurrent_events/TestConcurrentTwoBreakpointThreads.py",
line 19, in test
    self.do_thread_actions(num_breakpoint_threads=2)
  File
"/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/concurrent_base.py",
line 266, in do_thread_actions
    breakpoint_hit_count))
AssertionError: 2 != 3 : Expected 2 breakpoint hits, but got 3
Config=aarch64-/home/mgorny/llvm-project/build.arm64/bin/clang


It seems to be a problem in lldb/lldb-server logic somewhere that needs further
debugging.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Reply via email to