rkhoury
commented
2 months ago Something like https://marketplace.visualstudio.com/items?itemName=MBulli.SmartCommandlineArguments2022 would be amazing.
On Fri, 12 Apr 2024 at 19:03, bw-86 @.***> wrote:
First, thanks for your good work on WinDbg - it is by far the best debugger I know and a very important tool in my daily work.
For my work, I often launch executables from the debugger. These executables need complicated arguments - the last one I used had 218 characters. WinDbg supports me here be remembering the last used configuration.
However, I often have to debug multiple different processes - over time or at once. Just remembering the previous process data is not enough here, since I have to remember or look up my long argument lines each time, overwriting the previous one that might be needed again very soon.
It would be awesome if WinDbg could help me here even more by allowing me to give a name and reuse often needed "launch executable" configurations.
— Reply to this email directly, view it on GitHub https://github.com/microsoftfeedback/WinDbg-Feedback/issues/181, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACIAQQKEVCEE7UH5AY5AWLTY46PP7AVCNFSM6AAAAABGDYLLBKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTSNBXG42DKMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
First, thanks for your good work on WinDbg - it is by far the best debugger I know and a very important tool in my daily work.
For my work, I often launch executables from the debugger. These executables need complicated arguments - the last one I used had 218 characters. WinDbg supports me here be remembering the last used configuration.
However, I often have to debug multiple different processes - over time or at once. Just remembering the previous process data is not enough here, since I have to remember or look up my long argument lines each time, overwriting the previous one that might be needed again very soon.
It would be awesome if WinDbg could help me here even more by allowing me to give a name and reuse often needed "launch executable" configurations.