Your first project

Use a small executable you own. A program compiled with debug symbols is useful for comparing recovered information with known source. This walkthrough uses the upstream baseline’s menu names; VERIFY them in the Opcodex build you run.

Create and import

1. In the Project window, choose File → New Project.
2. Choose Non-Shared Project, then a local directory and a descriptive project name.
3. Use File → Import File and choose the executable.
4. Inspect the detected loader, processor, and compiler specification. Confirm before accepting.
5. Open the imported program in the CodeBrowser tool.
6. Review the initial analysis options and let analysis finish.

Read one function

Navigate to an entry point or a function you recognize. Keep the Listing and Decompiler visible together. Find one return value, a branch, and a call. Follow each in the Listing before accepting the higher-level interpretation.

Add a comment explaining an observed behavior. Rename one function only when the evidence supports its role. Save the program, close it, and reopen it to confirm your annotations persist.

Keep a reproducible record

Record the file’s hash, build flags if known, processor selection, analysis settings, and application version alongside your notes. Your project stores analysis state; it does not replace the original sample or your research record.

TODO: update screenshot with the first released Opcodex Project and CodeBrowser windows.

Next: Project handling and Importing.

---

Sources: Creating a Project, Importer.

Adapted from the Ghidra documentation (Apache 2.0).