WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@peace-maker
Copy link
Member

@peace-maker peace-maker commented Dec 3, 2025

On Windows there isn't one single debugger everyone uses but multiple ones with different purposes. Allow to choose the debugger to start when using windbg.attach by setting context.debugger. By default it autodetects which debugger is available trying windbgx then windbg. This could potentially be used to support lldb transparently too.

You can specify the path to the debuggers using context.windbg_binary and context.windbgx_binary too similarly to the context.gdb_binary property.

Prepare to support more debuggers than windbg.
This way we don't have to deal with shell escaping the dbgscript commands.
Allow to choose the debugger to start when using `windbg.attach`.
By default it autodetects which debugger is available.
You can specify the path to the debuggers using
`context.windbg_binary` and `context.windbgx_binary`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant