https://bugs.winehq.org/show_bug.cgi?id=54250
--- Comment #5 from ake.rehnman@gmail.com --- (In reply to Eric Pouech from comment #4)
I'm not sure to get fully your situation: what I understand is:
- you use wine from the build tree (compilation by yourself, wine not
installed)
- you run wine from the build tree
- in that case the system dlls from c:\windows\system in the prefix are
copied from the build tree, so it shouldn't change using one or the other
would you mind describing:
- how things are invoked (if different from above)
- what let you think you get the wrong debug info?
TIA
It is correct, I am running from the build tree. How ever if there is a *native* windows dll in the prefix it is by default overridden by the builtin version in the build tree. But when winedbg tries to load the symbol table for the builtin dll it was loading the debug symbols (or at least the exports) from the native windows dll.
With the "alternate patch" it looks like it is loading the debug symbols from the dll in the build tree. But the debug symbols still points to the wrong addresses.
I am going to dig a little more to see where it goes wrong...