You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a simple win32 executable test.exe, it depends on only kernel32.dll.
The module tree is same in DependenicesGUI, and in depends.
But the modules info list in DependenicesGUI, is like
C:\WINDOWS\SysWOW64\kernel32.dll i386 Dll
It should show the line:
C:\test.exe i386 Exe
The text was updated successfully, but these errors were encountered:
Agree that this is needed. DependencyWalker had up to four different indications on-screen that the module you were viewing the dependencies for was an AMD64 build versus an i386 build.
(Which was important to confirm, since DependencyWalker was dumb and would try and inspect 64-bit dependency images when viewing a 32-bit root module, and vice-versa.)
But DependenciesGui.exe has zero definitive indications on-screen for what architecture the root module was built for, let alone the other image details. I have to use the external PEView.exe to know for the root module the same information DependenciesGui.exe willingly shows for every other module.
Thanks for the pull request, and hopefully this gets in there at the next opportunity.
I have a simple win32 executable
test.exe
, it depends on only kernel32.dll.The module tree is same in DependenicesGUI, and in depends.
But the modules info list in DependenicesGUI, is like
It should show the line:
The text was updated successfully, but these errors were encountered: