Skip to content

Conversation

@themiswang
Copy link
Contributor

@themiswang themiswang commented Jan 15, 2026

Follow up for #15612
Since MacOS 10.5 and 11 does not have identity protected behavior option, we need to fall back to default behavior for backward compatibility.

#15393

#no-changelog

@gemini-code-assist
Copy link
Contributor

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

@themiswang
Copy link
Contributor Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds backward compatibility for Mach exception handling on older macOS versions by falling back to EXCEPTION_DEFAULT behavior. The changes are well-structured, using a union to handle different message formats and a behavior field to control the logic.

I've identified a critical bug where the code for finding the crashed thread (FIRCLSCrashedThreadLookup) incorrectly handles the new EXCEPTION_DEFAULT case, which could lead to a crash. I've also suggested refactoring to reduce code duplication and removing some leftover development comments. Please address the critical issue before merging.

@themiswang themiswang requested a review from mrober January 15, 2026 20:41
@themiswang themiswang marked this pull request as ready for review January 15, 2026 20:46
@themiswang
Copy link
Contributor Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly adds backward compatibility for older macOS versions by falling back to EXCEPTION_DEFAULT behavior for the Mach exception handler. The use of a union for different message formats and propagating the behavior flag is well done. However, I've identified a critical bug in FIRCLSCrashedThreadLookup where it fails to handle the EXCEPTION_DEFAULT case, which would prevent crash reporting on older macOS versions. I've provided a detailed explanation and a fix for this issue. Additionally, I've included a minor suggestion to improve logging for better debugging.

@themiswang
Copy link
Contributor Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly implements backward compatibility for Mach exception handling on older macOS versions by introducing a fallback to EXCEPTION_DEFAULT behavior. The use of a union to manage different message structures is appropriate. The code is generally well-structured, but I've pointed out a minor opportunity for code deduplication to improve maintainability, along with a small style fix.

@themiswang themiswang requested a review from ncooke3 January 15, 2026 21:16
Base automatically changed from machIPC to main January 16, 2026 19:28
@themiswang themiswang changed the title Address backwards compatibility Mach IPC identity protected address backwards compatibility Jan 16, 2026
@themiswang themiswang changed the title Mach IPC identity protected address backwards compatibility [Crashlytics] Mach IPC identity protected address backwards compatibility Jan 16, 2026
@themiswang themiswang merged commit 5125d5c into main Jan 16, 2026
51 checks passed
@themiswang themiswang deleted the machIPCConfigurable branch January 16, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants