Skip to content

Add interactive ct_updater inspection tools#38

Open
sirebacon wants to merge 6 commits intomiscusi-peek:mainfrom
sirebacon:miscusi-ct-updater
Open

Add interactive ct_updater inspection tools#38
sirebacon wants to merge 6 commits intomiscusi-peek:mainfrom
sirebacon:miscusi-ct-updater

Conversation

@sirebacon
Copy link
Copy Markdown

Summary

This adds a small interactive tooling layer under MCP_Server/ct_updater/tools plus the bridge helpers those tools
need.

The goal is to make ct_updater investigation and feature-discovery work easier when a table cannot be fixed by the
automatic pipeline alone.

What was added

  • ct_updater.tools.diff_scan
    Narrow repeated value scans across state changes.

  • ct_updater.tools.cluster_find
    Search for groups of nearby values that likely belong to the same structure.

  • ct_updater.tools.struct_dump
    Inspect memory around a resolved address or symbol as a candidate structure.

  • ct_updater.tools.ptr_walk
    Walk pointer graphs from a base address or symbol to find useful object paths.

  • ct_updater.tools.__main__
    Simple entry point for running the tools as python -m ct_updater.tools <tool>.

  • ct_updater.bridge helpers
    Added address resolution, scan wrappers, persistent named scan wrappers, typed reads, and write helpers needed by
    the tools.

Why

The existing updater pipeline is strong at validating and repairing known table entries, but there are still cases
where a human or AI needs to inspect live memory interactively:

  • exploring pointer paths from a known anchor
  • reducing harder manual-review cases into better evidence

These tools are intended to support that workflow directly from the ct_updater package instead of relying on one-off
local scripts.

Scope

work.

Notes

The new tooling is focused on live inspection through the existing CE bridge and reuses the updater bridge layer
rather than introducing separate ad hoc scripts.

If you want the maintainer to understand it even faster, add one short sentence near the top:

This is mainly a developer/operator tooling PR for ct_updater, not a change to end-user bridge behavior.

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.

1 participant