debugger Better workflow for adding binary views into the debugger binary view

Right now, when we start debugging, the binary view for the executable is rebased according to the actual base of the target. Then an empty debugger binary view is created, and all analysis data from the executable binary view is added to the debugger binary view. This works for now. However, it can be improved in multiple ways:

Allow the user to specify a mapping between a module and a binary view. When the debugger sees a module is loaded, the corresponding binary view will be automatically rebased and incorporated in the debugger view. This fits several workflows, e.g., when the user wishes to debug code in a DLL/so rather than the main executable. Or the the user wishes to debug code in several modules, e.g., in both the main executable and a particular DLL, etc. This is related to https://github.com/Vector35/debugger/issues/63.
Allow the user to not add any module binary views into the debugger binary view. https://github.com/Vector35/debugger/issues/206

A tentative way to reach this goal is to create an empty debugger binary view first, and add binary views for modules later.

Jun 27 '22 04:06 xusheng6

Closing in favor of https://github.com/Vector35/debugger/issues/477 and #206

May 11 '23 05:05 xusheng6

I forgot to close this when I made the comment https://github.com/Vector35/debugger/issues/207#issuecomment-1543368158. I am closing this now

May 24 '24 01:05 xusheng6