Re: Debugging winedbg

[Eric Pouech]

Ulrich Spoerlein wrote:
> Can anyone please explain this to me?

every module (in the Wine sense) is create with a .init section. the 
code in this section is executed as soon as the module is loader (by the 
ELF loader). But the code in this section expects a bit of Wine 
environment to be already present (basically the wine executable)

with preloading the .exe.so file, this code gets executed with the wine 
executable being loaded
> And what would be the easiest way to break into gdb on DEBUG_MainLoop?

add a breakpoint instruction at the start of DEBUG_MainLoop code
__asm__("int 3"); would do

A+