morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[PR #7249] [MERGED] docs(ghidra): clarify Objective-C Message Analyzer libobjc log #7746

New issue

Closed

opened 2026-11-03 13:40:05 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-03 13:40:05 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7249
Author: @BeqaKs
Created: 10/26/2026
Status: ✅ Merged
Merged: 10/27/2026
Merged by: @gensokyo-dev

Base: main ← Head: fix/docs-ghidra-objc-libobjc-message

📝 Commits (1)

e4de22a docs(ghidra): clarify Objective-C Message Analyzer libobjc log

📊 Changes

1 file changed (+15 additions, -0 deletions)

View changed files

📝 docs/installation.md (+15 -0)

📄 Description

Summary

Document that Ghidra's Try adding libobjc.dylib Objective-C Message Analyzer lines are non-fatal coverage loss when a Mach-O has no class metadata.
Point callers at failure_kind, REA_GHIDRA_DISABLED_ANALYZERS, and startup/heap knobs instead of searching for an on-disk libobjc.

Fixes #7208

Problem and expected behavior

Callers who see those Ghidra log lines have no REA-specific recovery path, and modern macOS does not ship /usr/lib/libobjc.A.dylib on disk.

Change and scope

Documentation-only clarification next to REA_GHIDRA_DISABLED_ANALYZERS in docs/installation.md. Structured bridge facts and upstream Ghidra changes remain out of scope. Maintainer scope decision not applicable.

Contract and boundary impact

Generated metadata: none
CLI/MCP: none

Expected effects:

Documentation or usability only; no target interaction.

Evidence and regression coverage

Source-derived diagnosis already recorded in #7208 (Ghidra analyzer canAnalyze vs type creation; REA headless import options).
Real Ghidra noclass / withclass verification not run here (Ghidra not installed in this environment).

Validation performed

Reviewed the new troubleshooting paragraph against the existing disabled-analyzers and startup-timeout sections.
npm run check:fast on the push path

Author readiness

Human owner: @BeqaKs

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for initial maintainer review.

Before merge

This PR addresses a concrete problem or an agreed enhancement.
Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7249 **Author:** [@BeqaKs](https://github.com/BeqaKs) **Created:** 10/26/2026 **Status:** ✅ Merged **Merged:** 10/27/2026 **Merged by:** [@gensokyo-dev](https://github.com/gensokyo-dev) **Base:** `main` ← **Head:** `fix/docs-ghidra-objc-libobjc-message` --- ### 📝 Commits (1) - [`e4de22a`](https://github.com/morluto/rea/commit/e4de22ac0bf56fe63982ffc6227f981614a955d9) docs(ghidra): clarify Objective-C Message Analyzer libobjc log ### 📊 Changes **1 file changed** (+15 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+15 -0) </details> ### 📄 Description ## Summary - Document that Ghidra's `Try adding libobjc.dylib` Objective-C Message Analyzer lines are non-fatal coverage loss when a Mach-O has no class metadata. - Point callers at `failure_kind`, `REA_GHIDRA_DISABLED_ANALYZERS`, and startup/heap knobs instead of searching for an on-disk libobjc. Fixes #7208 ## Problem and expected behavior Callers who see those Ghidra log lines have no REA-specific recovery path, and modern macOS does not ship `/usr/lib/libobjc.A.dylib` on disk. ## Change and scope Documentation-only clarification next to `REA_GHIDRA_DISABLED_ANALYZERS` in `docs/installation.md`. Structured bridge facts and upstream Ghidra changes remain out of scope. Maintainer scope decision not applicable. ## Contract and boundary impact - Generated metadata: none - CLI/MCP: none Expected effects: - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Source-derived diagnosis already recorded in #7208 (Ghidra analyzer `canAnalyze` vs type creation; REA headless import options). - Real Ghidra `noclass` / `withclass` verification not run here (Ghidra not installed in this environment). ## Validation performed - Reviewed the new troubleshooting paragraph against the existing disabled-analyzers and startup-timeout sections. - `npm run check:fast` on the push path ## Author readiness Human owner: @BeqaKs - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-11-03 13:40:05 +00:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#7746

No description provided.

Rows
Columns