the idea is to allow as much internal information into inner components.
to not burden all builds, the reflection level can be controlled
via the MOMO_REFLECTION_LEVEL (where 0 means no reflection code is
included).
more reflection variables will be introduced as needed.
for now, the memory manager's layout version is used to track whether
the memory layout is changed or not (at the lowest level).
the API consumer can use this to decide to refresh or not expensive
computations
The intention of this PR is not yet to extend/fix the GDB functionality,
but rather to get rid the `mini-gdbstub` dependency.
Its functionality should have been reimplemented as closely as possible.
The main reason for this is better portability and security fixes (there
are numerous OOB read/write vulnerabilities in `mini-gdbstub`)
Bumps [deps/googletest](https://github.com/google/googletest) from
`7d76a23` to `2b6b042`.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="2b6b042a77"><code>2b6b042</code></a>
Cast mutable lvalue references to const from testing::ResultOf</li>
<li><a
href="e4ece4881d"><code>e4ece48</code></a>
Enable safe matcher casts from <code>Matcher\<const T&></code>
to <code>Matcher\<T></code>.</li>
<li><a
href="504ea69cf7"><code>504ea69</code></a>
Document unexpected interaction with death test error code and
gmock.</li>
<li><a
href="4bbf80823c"><code>4bbf808</code></a>
Add UnpackStructImpl for structs with 20 fields.</li>
<li>See full diff in <a
href="7d76a231b0...2b6b042a77">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
The idea here is to start exposing various high level callbacks from
various sub components (syscalls, device io, etc.).
Consumer of `windows_emulator` can then hook into any callback.
Please give your feedback on this initial commit.
This PR provides configurable APISET data for the PEB
There are multiple ways the APISET data can be provided:
* host -> read the APISET from the host process
* file -> read the APISET from an external file
* w11 -> use an inbuilt dump from windows 11
* w10 -> use an inbuilt dump from windows 10
by default on windows it uses the "host" mode.
by default on linux/mac it uses the "w11" mode.
with the file mode you can use the dump-apiset tool to create a dump.
however the inbuilt w10 works fine on w11 so I don't expect it will be
needed.
