Improve GEF running under winedbg #1100
Draft
Conversation
This file contains 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
clubby789
force-pushed
the
wine-improvements
branch
from
b77fd79
to
b15d41b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Currently a draft as I'd like to improve this further but looking for initial feedback 馃檪 I'm not sure of the order in which hooks are run by GDB - in this current version, GEF tries to run
context, fails due to no arch being setup yet, then runs architecture detection.monitor memoutput provided by winedbgi386as an alias of X86GEF is currently awkward to use for debugging programs under Wine (specifically winedbg
--gdbmode). This is mostly due to incorrect architecture.