[PATCH 0/1] MR4710: winedbg: Add wow option in info share usage.
This patch just adds to the usage the "wow" keyword, which causes all modules to be listed instead of just the ones of the process executables architecture. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4710
From: Bernhard Übelacker <bernhardu(a)mailbox.org> --- programs/winedbg/info.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/programs/winedbg/info.c b/programs/winedbg/info.c index d95b286454a..825dd572cba 100644 --- a/programs/winedbg/info.c +++ b/programs/winedbg/info.c @@ -103,7 +103,7 @@ void info_help(void) " info reg Displays values of the general registers at top of stack", " info all-reg Displays the general and floating point registers", " info segments <pid> Displays information about all known segments", - " info share Displays all loaded modules", + " info [wow] share Displays all loaded modules", " info share <addr> Displays internal module state", " info stack [<len>] Dumps information about top of stack, up to len words", " info symbol <sym> Displays information about a given symbol", -- GitLab https://gitlab.winehq.org/wine/wine/-/merge_requests/4710
actually, I decided not to expose this as I don't like the syntax of the command IMO, we 'd better go with something like info share /multimachine (and open the door to other options as actual path of loaded module...). But that requires some more changes to winedbg lexer&parser to support simply command options. and, for the record, winedbg.man.in should be updated too. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4710#note_56191
Thanks for looking at this. Yes, I find the wow in the middle a bit strange too. So I am going to close this MR. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4710#note_56192
This merge request was closed by Bernhard Übelacker. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4710
participants (2)
-
Bernhard Übelacker -
eric pouech (＠epo)