Skip to content

Conversation

@kastiglione
Copy link

Some type systems require an execution context be available when working with types
(ex: Swift). This fixes memory read --type to support such type systems, by passing in
an execution context to GetByteSize(), instead of passing null.

rdar://158968545
(cherry picked from commit b574e63)

…ndObjectMemoryRead (NFC)

Some type systems require an execution context be available when working with types
(ex: Swift). This fixes `memory read --type` to support such type systems, by passing in
an execution context to `GetByteSize()`, instead of passing null.

rdar://158968545
(cherry picked from commit b574e63)
@kastiglione
Copy link
Author

@swift-ci test

@kastiglione
Copy link
Author

@swift-ci test

@kastiglione
Copy link
Author

the test failures are existing rebranch issues.

@kastiglione
Copy link
Author

@swift-ci test macOS

@kastiglione kastiglione merged commit 066aae1 into stable/21.x Sep 17, 2025
1 of 3 checks passed
@kastiglione kastiglione deleted the dl/lldb-Pass-execution-context-to-CompilerType-GetByteSize-in-CommandObjectMemoryRead-NFC branch September 17, 2025 21:35
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