http://bugs.winehq.org/show_bug.cgi?id=15206
Eric Pouech eric.pouech@orange.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech@orange.fr URL| |http://build.chromium.org/bu |http://build.chromium.org/bu%7Cildbot/snapshots/chromium- |ildbot/snapshots/chromium- |rel-xp/ |rel-xp/ |
--- Comment #1 from Eric Pouech eric.pouech@orange.fr 2008-09-09 15:06:25 --- currently winedbg still forces a pdb file to have correct timestamp (or guid) and age
timestamp (or guid) is generated the first time the pdb file is created the age starts at 1 and gets incremented at each recompilation of the project (without erasing the .pdb file)
so for consistency reasons, it's still usefull to force timestamp & age mapping between module and .pdb file
the good news is that now dbghelp knows how to load .pdb files which don't fully match.
the attached patch let winedbg turn on this feature (it's off by default) set ! module + is the command to be used in winedbg (I'm still unhappy with this patch, so still looking for a better solution)
you can very easily check that they match (tried the build 1712 and they match) do $WINE/tools/winedump/winedump -j debug chrome-win32/chrome.exe and $WINE/tools/winedump/winedump chrome_exe.pdb Age is the same (30 in my case, ditto for .dll). maybe there are older .pdb is the path ? (IIRC we do a depth first search first, so if you have other .pdb files in your pdb-bug directory, including in sub-sub-sub directories), you may get the error. however the algo should only return the matching file if any (patches committed yesterday)
for the rest, if I remove the flow of unsupported types (102c, 1137, 1139), I get err:ntdll:RtlpWaitForCriticalSection section 0x7d9679b4 "?" wait timed out in thread 0009, blocked by 0000, retrying (60 sec) error, which needs further investigations
will look further next days A+