forked from dotnet/coreclr
-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
ilasm.exe: Unhandled exception. RangeChecks instrumentation code detected an out of range array access #2
Labels
Comments
hmm, to continue we should also convert resources .res -> obj COFF-format (that will be placed in .rsrc section (PE)) HRESULT ConvertResource(const WCHAR * pszFilename, __in_ecount(cchTempFilename) WCHAR *pszTempFilename, size_t cchTempFilename, PEWriter &pewriter) that requires external cvtres.exe :( ...
DWORD dwExitCode;
fRet = RunProcess(tempResObj, pszFilename, &dwExitCode, pewriter);
if (!fRet)
{ // Couldn't run cvtres.exe
return PostError(CEE_E_CVTRES_NOT_FOUND);
}
... problem from here:
and where source code of this ? or license for simple distribution ? ~43 Kb (found in \Windows\Microsoft.NET\Framework\v4.0.30319) works fine
|
3F
added a commit
that referenced
this issue
Nov 3, 2016
``` * FIXED: Fixed using of cvtres (.res -> obj COFF-format) in mscorpe. Possible crash: #2 Related Issue: 3F/DllExport#17 * NEW: Implemented additional searching of the converters of resources: Environment PATH, local directory, and other additional from user path. Now it also can be wrapped like ` mytool.cmd -> cvtres.exe %* ` etc. * NEW: Added new /CVRES (/CVR) key to ilasm.exe `/CVRES=<path_to_file> Set path to cvtres tool: /CVR=cvtres.exe /CVR=tool\cvtres.cmd /CVR=D:\tool\` * NOTE: based on 4.5.22220.0 / coreclr 1.0.4 ^ ^ ^ ^ | | | |-- VER_FILEVERSIONREVISION | | |------- VER_FILEVERSIONBUILD | |---------- VER_FILEVERSIONMINOR |------------ VER_MAJORVERSION ```
3F
added a commit
to 3F/DllExport
that referenced
this issue
Nov 3, 2016
…h cvtres #17 Related Issue for coreclr: 3F/coreclr#2
has been resolved in v4.5.1
|
3F
added a commit
that referenced
this issue
Nov 3, 2019
* FIXED: ILDAsm. Fixed dasm.rc to correctly display list of available commands in console. * FIXED: ILAsm /CVRES key & trailing spaces from double quotes. Issue #5. * CHANGED: Updated coreclr 3.0.0 * CHANGED: ILDAsm. Added /NOBAR key (disassembly progress) to eliminate the difference between other versions. Helpful for projects like .NET DllExport that can use various versions. * CHANGED: Added the following tools to nupkg packages for related build processes. https://nuget.org/packages/ILAsm * tools\gnt.bat - https://github.com/3F/GetNuTool * tools\hMSBuild.bat - https://github.com/3F/hMSBuild * CHANGED: Updated original fixes for ILAsm & ILDAsm that points to coreclr 3 release. * NOTE: Don't forget to provide compatible converter of resources to obj COFF-format when using ILAsm. Use /CVRES (/CVR) key. Related issue: #2 * NOTE: MSBuild Properties for nupkg packages: ``` * $(ILAsm_RootPkg) - path to root folder of this package after install. * $(ILAsm_PathToBin) - path to `\bin` folder., eg.: $(ILAsm_PathToBin)Win.x64\ilasm.exe ``` * NOTE: PDB files (240 MB+) are available through GitHub Releases: https://github.com/3F/coreclr/releases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For version v1.0.4 - 51131a5 - 4.5.22220.0
both x86 and x64
seems solves problem 3F/DllExport#17
but, after:
The text was updated successfully, but these errors were encountered: