aboutsummaryrefslogtreecommitdiff
path: root/src/yuzu/debugger/wait_tree.cpp
diff options
context:
space:
mode:
authorLioncash <mathew1800@gmail.com>2018-12-02 02:00:11 -0500
committerLioncash <mathew1800@gmail.com>2018-12-02 03:41:49 -0500
commit9a1400b30d4751035b399b6a143554dd2abbd66a (patch)
tree5657b2824c89590e4cccd2908b997eac8f0d53cd /src/yuzu/debugger/wait_tree.cpp
parenta3ecd8177ff56985e6557b2302112d4b526e3399 (diff)
svc: Use the current process' handle table for retrieving the process instance to act upon
The kernel uses the handle table of the current process to retrieve the process that should be used to retrieve certain information. To someone not familiar with the kernel, this might raise the question of "Ok, sounds nice, but doesn't this make it impossible to retrieve information about the current process?". No, it doesn't, because HandleTable instances in the kernel have the notion of a "pseudo-handle", where certain values allow the kernel to lookup objects outside of a given handle table. Currently, there's only a pseudo-handle for the current process (0xFFFF8001) and a pseudo-handle for the current thread (0xFFFF8000), so to retrieve the current process, one would just pass 0xFFFF8001 into svcGetInfo. The lookup itself in the handle table would be something like: template <typename T> T* Lookup(Handle handle) { if (handle == PSEUDO_HANDLE_CURRENT_PROCESS) { return CurrentProcess(); } if (handle == PSUEDO_HANDLE_CURRENT_THREAD) { return CurrentThread(); } return static_cast<T*>(&objects[handle]); } which, as is shown, allows accessing the current process or current thread, even if those two objects aren't actually within the HandleTable instance.
Diffstat (limited to 'src/yuzu/debugger/wait_tree.cpp')
0 files changed, 0 insertions, 0 deletions