On Monday 15 December 2003 03:45 pm, Mike Hearn wrote:
On Mon, 2003-12-15 at 21:04, Gregory M. Turner wrote:
FYI, I don't know if this makes things any different, but I simply pointed WINELOADER to "wine", not wine-{p,k}thread, and it seems fine... what errors?
[mike@e-ucs036 tests]$ WINELOADER=/opt/wine/bin/wine winedbg ie6setup.exe fixme:console:SetConsoleCtrlHandler (0x403884e0,1) - no error checking or testing yet WineDbg starting on pid a Breakpoint 1 at 0x01005ae4 Invalid address, can't set breakpoint You can turn on deferring breakpoints by address by setting $CanDeferOnBPByAddr to 1 Loaded debug information from ELF '/opt/wine/bin/wine-pthread' ((nil)) Breakpoint 2 at 0x3ffa9ea0 (_end+0x2fe95ea0) Loaded debug information from ELF '/opt/wine/lib/libwine.so.1' (0x10114000) *** Invalid address 0xf441000 (pe_load+0xf32d000 in wine-pthread) *** Invalid address 0xf6db000 (pe_load+0xf5c7000 in wine-pthread) *** Invalid address 0xf6b5000 (pe_load+0xf5a1000 in wine-pthread) *** Invalid address 0xf6dc000 (pe_load+0xf5c8000 in wine-pthread) *** Invalid address 0x3f554000 (_end+0x2f428580)
...and so on...
[mike@e-ucs036 tests]$ WINELOADER=wine winedbg ie6setup.exe wine: could not exec wine-pthread
So, I dunno really...
hmm, one minor difference... I use WINELOADER=/opt/wine/bin/wine (we happen to have the same wine prefix)... perhaps the word "simply" above was too strong ;)