165e3a9936
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. |
||
|---|---|---|
| .. | ||
| Android | ||
| Core | ||
| DSPSpy | ||
| DSPTool | ||
| PCH | ||
| UnitTests | ||
| VSProps | ||
| .clang-format | ||
| CMakeLists.txt | ||
| dolphin-emu.sln | ||