diff options
| author | Léo Lam <leo@innovatetechnologi.es> | 2016-11-18 22:06:42 +0100 |
|---|---|---|
| committer | Léo Lam <leo@innovatetechnologi.es> | 2016-11-19 00:11:41 +0100 |
| commit | 165e3a9936e456adfb19ad2783b778635b7bc4ca (patch) | |
| tree | 422a2c0c1679fdfc0e863f8cf0b205b18473b28a /Source/Core/VideoBackends/Vulkan/ObjectCache.cpp | |
| parent | d3710d5cff432f0002725a8e2f24d5a0129f5966 (diff) | |
IPC_HLE: Fix emulated BT crash (uninitialised memory)
When the emulated BT device is created, m_HCIEndpoint (which is a
CtrlBuffer)'s m_cmd_address is not initialised to 0. So it ends up
being a random value. This is normally not an issue… but the
emulated Bluetooth code relies on m_cmd_address to know whether the
HCI endpoint is still valid.
This is a problem with ES_Launch, because the bt_emu class is
destructed and re-constructed, and while m_cmd_address is still
uninitialised, the ES_Launch code disconnects all Wii remotes,
which triggers a HCI event and hence the bug.
Diffstat (limited to 'Source/Core/VideoBackends/Vulkan/ObjectCache.cpp')
0 files changed, 0 insertions, 0 deletions