Don't free breakpoints racing the debugger walk#52
Merged
Conversation
Prevent the use-after-free crash when a gdb client disconnects while the emulator is running.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On gdb client disconnect the network thread freed the breakpoint list directly; if the emulator was running this raced
debugger_check()'s walk on the emulator thread, dereferencing a freed breakpoint (EXC_BAD_ACCESSinbreakpoint_check). The cleanup now frees directly only while the emulator is parked (gdbserver_trapped), otherwise defers the free to the emulator thread viadebugger_breakpoints_remove_pending, honored at a safe point indebugger_check().