Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not show a backtrace. This makes it significantly more difficult to debug the crash. Is anyone else experiencing this? I'll run a regression test as soon as I can.
wine: Unhandled page fault on read access to 0x00000000 at address 0x7ebfeb70 (thread 0011), starting debugger... Modules: Cannot get info on module while no process is loaded Threads: process tid prio (all id:s are in hex) 00000013 00000021 0 00000020 0 0000001e 0 0000001b 0 00000019 0 00000018 0 00000017 0 00000016 0 00000014 0 00000010 (D) (null) 00000023 0 00000022 0 00000012 0 00000011 0 0000000a 0000000c 0 0000000b 0
On 10/2/06, James Hawkins truiken@gmail.com wrote:
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not show a backtrace. This makes it significantly more difficult to debug the crash. Is anyone else experiencing this? I'll run a regression test as soon as I can.
Update: running apps that crash in winedbg gives the proper backtrace.
James Hawkins wrote:
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not show a backtrace. This makes it significantly more difficult to debug the crash. Is anyone else experiencing this? I'll run a regression test as soon as I can.
what's the format of your AeDebug registry key ? it seems it tries to start a program while it's supposed to attach to a running program A+
On 10/2/06, Eric Pouech eric.pouech@wanadoo.fr wrote:
James Hawkins wrote:
Hey guys,
Since very recently, any time we get a crash in Wine, winedbg does not show a backtrace. This makes it significantly more difficult to debug the crash. Is anyone else experiencing this? I'll run a regression test as soon as I can.
what's the format of your AeDebug registry key ? it seems it tries to start a program while it's supposed to attach to a running program A+
Auto = '1' Debugger = 'winedbg --auto %ld %ld'
James Hawkins wrote:
Auto = '1' Debugger = 'winedbg --auto %ld %ld'
does the attached patch help ?
[WineDbg]: fixed the auto mode
From: Eric Pouech eric.pouech@wanadoo.fr
---
programs/winedbg/info.c | 2 +- programs/winedbg/tgt_active.c | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/programs/winedbg/info.c b/programs/winedbg/info.c index d2042bf..c5b7b1e 100644 --- a/programs/winedbg/info.c +++ b/programs/winedbg/info.c @@ -204,7 +204,7 @@ void info_win32_module(DWORD base) int i, j, num_printed = 0; DWORD opt;
- if (!dbg_curr_process || !dbg_curr_thread) + if (!dbg_curr_process) { dbg_printf("Cannot get info on module while no process is loaded\n"); return; diff --git a/programs/winedbg/tgt_active.c b/programs/winedbg/tgt_active.c index af619a0..48f1ec9 100644 --- a/programs/winedbg/tgt_active.c +++ b/programs/winedbg/tgt_active.c @@ -867,7 +867,8 @@ enum dbg_start dbg_active_auto(int argc, argc--; argv++; ds = dbg_active_attach(argc, argv); if (ds != start_ok) return ds; - hFile = parser_generate_command_file("echo Modules:", "info share", + hFile = parser_generate_command_file("backtrace", + "echo Modules:", "info share", "echo Threads:", "info threads", NULL); } @@ -923,6 +924,9 @@ enum dbg_start dbg_active_auto(int argc, else return start_error_parse; if (hFile == INVALID_HANDLE_VALUE) return start_error_parse;
+ if (dbg_curr_process->active_debuggee) + dbg_active_wait_for_first_exception(); + dbg_interactiveP = TRUE; parser_handle(hFile);
On 10/2/06, Eric Pouech eric.pouech@wanadoo.fr wrote:
James Hawkins wrote:
Auto = '1' Debugger = 'winedbg --auto %ld %ld'
does the attached patch help ?
[WineDbg]: fixed the auto mode
From: Eric Pouech eric.pouech@wanadoo.fr
I had to apply it by hand, but once I did it worked. Thanks Eric.
-
Eric Pouech -
James Hawkins