This patch should change the module list in the automatic backtraces from "info share" to "info wow share". That way all loaded modules should get listed instead of just the process native ones.
From: Bernhard Übelacker bernhardu@mailbox.org
--- programs/winedbg/tgt_active.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/programs/winedbg/tgt_active.c b/programs/winedbg/tgt_active.c index 17578857133..5fdce09de61 100644 --- a/programs/winedbg/tgt_active.c +++ b/programs/winedbg/tgt_active.c @@ -909,7 +909,7 @@ enum dbg_start dbg_active_auto(int argc, char* argv[]) break; }
- input = parser_generate_command_file("echo Modules:", "info share", + input = parser_generate_command_file("echo Modules:", "info wow share", "echo Threads:", "info threads", "info system", "detach",
Even when the 'info wow share' is likely to go away, might this patch be useful until this happens?
I think it's ok to use that 'ugly' command line internally if there's a need for it.
which raises the next question: is this something useful to do?
on one hand,
* a 'regular' wow64 session will add the default 64 modules used in wow64 (not very interesting) * it's a bit more verbose
on the other hand,
* under new wow setup, it would show the ELF/Mach-O modules (which could be in some cases of interest) for a 32bit debuggee (info that we loose compared to old wow) * under old & new wow setup, it would show if using modules from different machine (in the bug report you're referring to, a 64bit process is making use of a 32bit DLL)
since this command is used to get a grasp of context where a crash occurred, I'm rather a bit inclined towards the option of adding it.
-
Bernhard Übelacker -
Bernhard Übelacker (＠bernhardu)
-
eric pouech (＠epo)