problems with winedbg

Sylvain Petreolle spetreolle at
Sun Aug 4 19:51:06 CDT 2002

Hi list,

updating wine to current cvs shows that stg could be broken in winedbg.
Running programs that crash and go to debugger make winedbg jump
nowhere in winedbg's data. This happens with several programs I tested
(windows / dos programs), and the backtrace is always the same. The
programs all complain about a read access fault at 0x0815cbe4 (yes,
always the same adress) and show this backtrace :

Unhandled exception: page fault on read access to 0x0815cbe4 in 32-bit
code (0x40388450).
In 32-bit mode.
0x40388450 ( in addl
=>0 0x40388450 ( in
  1 0x40387f53 ( in
  2 0x40391e98 ( in
  3 0x40392142 ( in
  4 0x403924d7 ( in
  5 0x4037b16b (winedbg.exe.EntryPoint+0x37 in winedbg.exe)
  6 0x400c05ff (start_process+0x23b [process.c] in
  7 0x400c43a1 (call_on_thread_stack+0x79 [sysdeps.c] in (ebp=404e6ff4)
  8 0x400c44dc (SYSDEPS_CallOnStack+0x14 in

Do You Yahoo!? -- Une adresse gratuite et en français !
Yahoo! Mail :

More information about the wine-users mailing list