Skip to content

[lldb] Update two API tests to fix x86 Darwin failures (#121380) #9828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

jasonmolenda
Copy link

The Intel Darwin CI bots had their Xcode updated, which brought in a debugserver with Brendan Shanks' change from September 7281e0c
llvm#108663 where four general purpose registers are sent by debugserver when in certain process states. But most processes (nearly all in the testsuite) do not have these registers available, so we will get register read failures when requesting those four. These two tests would flag those as errors. There would have been an additional problem with the g/G packet (which lldb doesn't use w/ debugserver, but the testsuite tests) if placeholder values were not included in the full register context bytes; I fixed that issue with the SME patch to debugserver recently already.

(cherry picked from commit 5056a4b)

The Intel Darwin CI bots had their Xcode updated, which brought in a
debugserver with Brendan Shanks' change from September
7281e0c
llvm#108663 where four general
purpose registers are sent by debugserver when in certain process
states. But most processes (nearly all in the testsuite) do not have
these registers available, so we will get register read failures when
requesting those four. These two tests would flag those as errors. There
would have been an additional problem with the g/G packet (which lldb
doesn't use w/ debugserver, but the testsuite tests) if placeholder
values were not included in the full register context bytes; I fixed
that issue with the SME patch to debugserver recently already.

(cherry picked from commit 5056a4b)
@jasonmolenda jasonmolenda requested a review from a team as a code owner January 14, 2025 09:17
@jasonmolenda
Copy link
Author

@swift-ci test

@jasonmolenda
Copy link
Author

@swift-ci test macos

@jasonmolenda
Copy link
Author

nb this is failing on macos,

Failed Tests (1):
  lldb-api :: commands/register/register/register_command/TestRegisters.py

the swift CI bot is probably using the debugserver from an installed Xcode and it's not the newest GM'ed Xcode which has the intel register changes. need to look more closely. I wrote the patch assuming testing was with in-tree debugserver or the newest GM'ed Xcode.

changes when you use a system-debugserver depending
on whether you have the current Xcode (expected) or
an older Xcode (unexpected), and currently the
swift CI bots are using an older Xcode.
@jasonmolenda
Copy link
Author

@swift-ci test

@JDevlieghere JDevlieghere merged commit 2f27117 into swiftlang:swift/release/6.1 Jan 15, 2025
3 checks passed
@jasonmolenda jasonmolenda deleted the testsuite-fixes-for-newer-intel-debugserver branch January 15, 2025 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants