-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exports/Imports table in win32 shell ext page showing blank rows #413
Comments
I've seen the ListView issue happen occasionally but I thought I had that fixed... Can you post the build errors you're encountering with later versions of Visual Studio and/or the Windows 10 SDK? I've been using MSVC 2022 for release builds (v143 for most architectures; v141_xp for i386) without any issues. |
I've managed to reproduce this error in the debug build, and it isn't the same issue I was seeing before. The issue I was seeing before was on all ListViews. This one seems to just be for the import/export tables. |
Commit 59c3d23 should fix this. |
Reopening because I'd still like to know what was causing build issues with later versions of MSVC, since I can't reproduce it here. |
@GerbilSoft sorry for my late replay :( this is my binlog obtained from msbuild: https://litter.catbox.moe/rtz3ug.binlog **u can use https://msbuildlog.com/ to open *.binlog |
…f Windows headers have already been included. I can't reproduce this issue locally, but I received a report about this from a user who was using the Windows 11 SDK (10.0.22621.0) with MSVC 2022. See #413: Exports/Imports table in win32 shell ext page showing blank rows Reported by @ksharperd.
Looks like it was a conflict between the EXE parser's custom headers and the Windows SDK headers, though I'm not sure why it didn't show up on my system, even with the same MSVC and SDK version... Try building the latest commit with MSVC 2022 and SDK 10.0.22621.0 and let me know if you encounter any more errors. |
latest commit seems solve redefinition error, but build still encountered some errors: https://litter.catbox.moe/qc1yic.binlog |
…d in the Windows SDK. See #413: Exports/Imports table in win32 shell ext page showing blank rows Reported by @ksharperd.
It seems IMAGE_IMPORT_DIRECTORY is not defined in the Windows SDK. Reworked that so it's unconditionally defined by exe_pe_structs.h. |
…lso not present in the Windows SDK. See #413: Exports/Imports table in win32 shell ext page showing blank rows Reported by @ksharperd.
...and the IMAGE_DATA_DIRECTORY_* constants. |
…ined in the Windows SDK. See #413: Exports/Imports table in win32 shell ext page showing blank rows Reported by @ksharperd.
I believe that should be all of it now. Try building again. |
still catch some build errors, i can successfully build with my addition changes: https://litter.catbox.moe/g688xp.patch |
Pushed some more changes that should hopefully fix everything that was in that patch. |
thanks for investigate! but i still got these errors while building latest commit
should we add a overload for it? |
Should be working now. Please re-test and let me know if there are any other issues. |
unfortunately not :( |
Added another attempt at a workaround in commit ed2999e. Please try that out and let me know how it goes. |
I can confirm that this commit fixes the build issue, but try to open shell ext page will crash the explorer with 0xc0000005. *Edit: romdata-5.dll cause the crash, i will attach this file alongside with other components since i'm not comfortable with Windows debugging : ) |
From WinDbg:
From Visual Studio 2022:
Visual Studio doesn't seem to want to map the dump file and PDBs to the original source code, which is making this difficult to debug. I'll try to reproduce it with a local build. EDIT: I can't seem to reproduce this locally... In Visual Studio, can you use "Attach to Process", attach to explorer.exe, then try to reproduce the crash and take a screenshot of where Visual Studio shows the exception? |
yes i can see the cause: RpFile_scsi_win32.cpp:67 btw, hitting exception seems make everything freeze except cursor(even Visual Studio itself is unclickable), but i can still catch the error fortunately 😂 |
…enameW, not d->filename. d->filename is usually nullptr at this point on Windows. Also, ensure that d->filenameW is neither NULL nor an empty string. It shouldn't happen, but a redundant check is better than a crash. See #413: Exports/Imports table in win32 shell ext page showing blank rows Reported by @ksharperd.
Looks like the problem is RpFile_scsi_win32 wasn't updated to use d->filenameW. I'm not sure why I wasn't hitting this issue locally... Updated it to use d->filenameW, plus a NULL pointer check. |
yeah, it fix the crash but rom properties tab just disappear. i guess we need more work to make newer win-sdk version work, a long journey... isn't it? 🤷♂️ |
Issue
Exports/Imports table in win32 shell ext page showing blank rows, but Copy/Export works fine.
OS Version
Windows 10 Build 19045.4291
Details
I'm using locally built version(with commit fcfeea7) without any change.
configured with
cmake . -G "Visual Studio 14 2015" -A "x64" -DCMAKE_SYSTEM_VERSION="8.1" -DCMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION="8.1"
and build with 'Release' config since there is a build error when i try to build with WinSDK 10 or newer Visual Studio version.**this issue has occurred two or three weeks ago though.
The text was updated successfully, but these errors were encountered: