package bap-stub-resolver

Not available on OCaml 5.5
  1. Overview
  2. Docs
Identifies and manages stub functions in a binary

Install 

dune-project
 Dependency

github.com Edit opam file Versions (4)

Authors

  1. B
    BAP Team

Maintainers

  1. I
    Ivan Gotovchits <ivg@ieee.org>

Sources

v2.5.0.tar.gz
sha256=9c126781385d2fa9b8edab22e62b25c70bf2f99f6ec78abb7e5e36d63cfa4174
md5=5abd9b3628b43f797326034f31ca574f

Description

Identifies functions that are stubs and redirects calls to stubs to the calls to the implemenations, in case if the latter is present in the binary.

A stub is piece of binary code that is used to call a function implementation. Most commonly stubs are employed for external functions, whose implementation is later loaded from some library, however some ABIs are using stubs for internal functions, in case if they have external linkage.

Added to opam-repository:

Dependencies (14)

  1. ogre = "2.5.0"
  2. bitvec-sexp = "2.5.0"
  3. bitvec-order = "2.5.0"
  4. bitvec = "2.5.0"
  5. bap-std = "2.5.0"
  6. bap-relation = "2.5.0"
  7. bap-main = "2.5.0"
  8. bap-knowledge = "2.5.0"
  9. bap-core-theory = "2.5.0"
  10. bap-abi = "2.5.0"
  11. ounit
  12. ppx_bap
  13. ocaml >= "4.08.0"
  14. core_kernel >= "v0.14" & < "v0.16"

Dev Dependencies

None

Optional Dependencies

None

Used by (1)

  1. bap-core >= "2.5.0"

Conflicts

None

Build status

Results of building bap-stub-resolver with each compiler on check.ci.ocaml.org, run of against opam-repository 8a77e58. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
2.5.0 (this version) good good n/a n/a n/a
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure