jeffl a écrit :
Eric, it is number one.
Eg:
1 0x40912b8f GDI_GetObjPtr+0x197(handle=0x107f, magic=0x)
[/winf/dlls/gdi/gdiobj.c:861] in gdi32 (0x4073fcac)
2 0x40912c71 DeleteObject+0x39(obj=0x107f)
[/winf/dlls/gdi/gdiobj.c:919] in gdi32 (0x4073fccc)
as it was last week and
3 0x40915afd GD
Eric, it is number one.
Eg:
1 0x40912b8f GDI_GetObjPtr+0x197(handle=0x107f, magic=0x)
[/winf/dlls/gdi/gdiobj.c:861] in gdi32 (0x4073fcac)
2 0x40912c71 DeleteObject+0x39(obj=0x107f)
[/winf/dlls/gdi/gdiobj.c:919] in gdi32 (0x4073fccc)
as it was last week and
3 0x40915afd GDI_GetObjPtr+0x105
lats a écrit :
In the last week WINEDBG has stopped outputting the file/path and
linenumber of entries in the backtrace. Does anyone know what happened?
Do you mean that either:
1/ backtraces (for a given program, in a given situation) used to provide file
& line number
2/ some (random) backtrac
In the last week WINEDBG has stopped outputting the file/path and
linenumber of entries in the backtrace. Does anyone know what happened?
Jeff
