Add explicit exceptional control flow instruction

Open
#351 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, linux

Research direction

Start by reading the linked Linux exception-tables documentation and the issue's description of get_user fault recovery. Determine how Binary Ninja's instruction representation could express the access and recovery relationship; done means a reviewed design and API instruction specification that captures this documented control flow.

Written by the indexing model from the issue text.

Description

Component: Core Effort: High Impact: Medium

In the Linux kernel, there is a generic fault-recovery mechanism [1] that is used in things like get_user (read data through a user-space pointer) to recover from a faulting memory access. The access is implemented in assembly, and a recovery code is also specified in the assembly, and a table entry is added to a seperate section the "links" the two. It would be nice if Binary Ninja were aware of these special and documented control-flows, and had an instruction for expressing them. I think this type of instruction would be more generally useful in the future.

[1] http://lxr.free-electrons.com/source/Documentation/x86/exception-tables.txt

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.