When I using winedbg why doesn't it show me the sourcecode? It always says that the source is not availabel through a configured DOS drive. Does that mean I have to put the files in a path that will be accessible by wineWindows?
When I try to debug agent I set a conditional breakpoint on WINPROC_CallWndProc. When the condition is hwnd == x then it works. When the condition is msg == x hten the breakpoint is never triggered, though it should because the backtrace tells me that the value, I set for the condition, has been used before that call. Either the backtrace is wrong or somehow winedbg misses the condition.
Gerhard W. Gruber wrote:
When I using winedbg why doesn't it show me the sourcecode? It always says that the source is not availabel through a configured DOS drive. Does that mean I have to put the files in a path that will be accessible by wineWindows?
yes
When I try to debug agent I set a conditional breakpoint on WINPROC_CallWndProc. When the condition is hwnd == x then it works. When the condition is msg == x hten the breakpoint is never triggered, though it should because the backtrace tells me that the value, I set for the condition, has been used before that call. Either the backtrace is wrong or somehow winedbg misses the condition.
this is a bug in winedbg (we haven't set up yet the expression evaluation context when the evaluate the bp condition, hence some weird results) please use winedbg's --gdb option until I find some time to fix it
A+
On Sun, 25 May 2003 18:35:53 +0200, Eric Pouech pouech-eric@wanadoo.fr wrote:
this is a bug in winedbg (we haven't set up yet the expression evaluation context when the evaluate the bp condition, hence some weird results)
Thanks.
please use winedbg's --gdb option until I find some time to fix it
winedbg -gdb <program>
When I use this then winedbg only shows me all options that I could set and exits with "unknown option -gb".
When I use this then winedbg only shows me all options that I could set and exits with "unknown option -gb".
you need to run it as winedbg -- --gdb A+
this is a bug in winedbg (we haven't set up yet the expression evaluation context when the evaluate the bp condition, hence some weird results) please use winedbg's --gdb option until I find some time to fix it
A+
does this work ? (the patch is ugly, but it doesn't matter too much) A+ Index: winedbg.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/programs/winedbg/winedbg.c,v retrieving revision 1.11 diff -u -u -r1.11 winedbg.c --- winedbg.c 22 May 2003 03:44:01 -0000 1.11 +++ winedbg.c 25 May 2003 16:53:41 -0000 @@ -407,6 +407,7 @@ }
DEBUG_LoadEntryPoints("Loading new modules symbols:\n"); + DEBUG_BackTrace(DEBUG_CurrTid, FALSE);
if (!force && is_debug && DEBUG_ShouldContinue(&addr, code,
On Sun, 25 May 2003 18:54:49 +0200, Eric Pouech pouech-eric@wanadoo.fr wrote:
does this work ? (the patch is ugly, but it doesn't matter too much)
Yes. This appears to work. :)
But I must say that winedbg seems pretty unstable if you really try to use it.
-
Eric Pouech -
Gerhard W. Gruber