Home > Archive > VC Utilities > October 2005 > Dependency Walker can't open .exe file (VC++6 SP6)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Dependency Walker can't open .exe file (VC++6 SP6)
|
|
| Norman Diamond 2005-10-10, 9:58 pm |
| Visual Studio 6 SP6 includes Dependency Walker. When Windows Explorer is
showing the filename and icon for an .exe file, a right-click and "View
Dependencies" opens Dependency Walker. Ordinarily this tool displays the
..exe file's dependencies on dlls, so for example the user can verify if the
actual dlls being used are the expected instances.
But today it didn't. A right-click and "View Dependencies" opened
Dependency Walker. Dependency Walker is showing a corrupted filename with a
yellow circle and question mark, and an error message "File not found in
local directory or search path."
The correct filename is perfectly good Japanese. This is on Windows XP SP2
Japanese, running Visual Studio 6 SP6 Japanese. Visual Studio reads,
displays, and compiles source files that have the same base filename but
extension of .cpp or .h instead of .exe. Visual Studio writes the .exe file
correctly. Windows Explorer shows all of the filenames correctly. A
double-click executes the file correctly. Only Dependency Walker messes up.
The filename consists of nine characters (six Kanji and three kana), and the
extension .exe. Dependency Walker corrupts one of the Kanji and one of the
kana, and of course there doesn't exist a file with the resulting corrupted
name. The actual characters are $BMQ(B (a Kanji pronounced yo-o, meaning "for")
and $B%D(B (full-width full-size katakana tsu).
(Due to the second of these two bugs, Dependency Walker wouldn't even be
capable of calling itself a tool, $B%D!<%k(B)
| |
| Jochen Kalmbach [MVP] 2005-10-11, 3:59 am |
| Hi Norman!
> The filename consists of nine characters (six Kanji and three kana), and
> the extension .exe. Dependency Walker corrupts one of the Kanji and one
> of the kana, and of course there doesn't exist a file with the resulting
> corrupted name. The actual characters are $BMQ(B (a Kanji pronounced yo-o,
> meaning "for") and $B%D(B (full-width full-size katakana tsu).
It seems that dependency-walker is not unicode-enabled :-(
(the same problem with the version from http://www.dependencywalker.com/)
You can try to contact help@dependencywalker.com to get some answers
about this problem...
--
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
| |
| Norman Diamond 2005-10-11, 3:59 am |
| I don't need Unicode for this one. That's why I mentioned that Windows XP
SP2 and Visual Studio 6 SP6 are both Japanese products. The environment on
this system is 100% Japanese. ANSI code page 932 is fine for these, and
they don't have to know that some parts of XP's internal operations are
Unicode. The problem is only Dependency Walker. This is the Dependency
Walker that came in the Visual Studio 6 Japanese package, possibly updated
by SP6.
Also consider that Dependency Walker displayed seven of the nine Japanese
characters correctly, it only screwed up two of them. I don't think
Dependency Walker decided to use a code page other than 932, it's just
messed up.
"Jochen Kalmbach [MVP]" <nospam-Jochen.Kalmbach@holzma.de> wrote in message
news:%23JrvWrizFHA.1252@TK2MSFTNGP09.phx.gbl...
> Hi Norman!
>
>
> It seems that dependency-walker is not unicode-enabled :-(
> (the same problem with the version from http://www.dependencywalker.com/)
>
> You can try to contact help@dependencywalker.com to get some answers
> about this problem...
>
> --
> Greetings
> Jochen
>
> My blog about Win32 and .NET
> http://blog.kalmbachnet.de/
|
|
|
|
|