How does one tell what DLL contains a particular
segment of 16 bit code in winedbg?
For instance, there's a nice juicy exception that happens
towards the end of the Resource Hunter installer,
available as a free trial download at http://www.boilsoft.com/rchunter.html
In wine = win2k mode, it
Dan Kegel wrote:
How does one tell what DLL contains a particular
segment of 16 bit code in winedbg?
that's no longer supported in winedbg (we don't generate in Wine the
native 16 bit DLL loading events, so we don't catch them in winedbg)
a way to do it is to trace +module and get the address
