[all-commits] [llvm/llvm-project] 4a6696: [lldb][test] Fix test_listener_event_process_state...

David Spickett via All-commits all-commits at lists.llvm.org
Wed Sep 30 02:38:26 PDT 2026


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4a66966a8a523eccf7b1a3552b0f2a20124abc76
      https://github.com/llvm/llvm-project/commit/4a66966a8a523eccf7b1a3552b0f2a20124abc76
  Author: David Spickett <david.spickett at arm.com>
  Date:   2026-09-30 (Wed, 30 Sep 2026)

  Changed paths:
    M lldb/test/API/api/multithreaded/test_listener_event_process_state.cpp

  Log Message:
  -----------
  [lldb][test] Fix test_listener_event_process_state (TestMultithreaded.py) on Windows on Arm (#227605)

This test expects to be sent function names by another thread. Function
names are allowed to be null, but the sending thread only sent them when
they were non-null.

On Windows on Arm, for whatever reasion, all the functions have no name
during the test. This is despite lldb being able to show them:
```
* thread #1, stop reason = breakpoint 1.1
   * frame #0: 0x00007ff71d191008 inferior_program`int next(void) at inferior.cpp:6:13
     frame #1: 0x00007ff71d19107c inferior_program`main at inferior.cpp:13:9
     frame #2: 0x00007ff71d1cc994 inferior_program`
```
The test is not about whether we parse debug info properly, and I am not
about to dive into that anyway. So I think it's better to adapt the test
to only care that some function was found. The function's name is just a
token to say that, empty or otherwise.



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


More information about the All-commits mailing list