I installed Clang stable build 7.01 for windows 64 bit pre-built binaries on my Windows 7 machine and i cannot get it to run. By that i mean it immediately core dumps before even parsing the command line options. The dump file doesnt help me much. Here is the output:
LLVM ERROR: out of memory
Wrote crash dump file "C:\Users\Lewis\AppData\Local\Temp\clang.exe-84805c.dmp"
0x0000000140A7F506 (0x0000000000000016 0x00000001425A4EFF 0x0000000140A7F500 0x0000000000000000)
0x00000001425A5275 (0x0000000000B9DD01 0x0000000000000000 0x0000000000000000 0x0000000000DBEB90)
0x000000014259CA84 (0x0000000000000002 0x0000000000DBEB90 0x0000000000B9DA60 0x00000001425E0B3E)
0x0000000140A7D55B (0x0000000000DB8880 0x0000000000B9DCC8 0x0000000000B9DCD8 0x0000000000000000)
0x0000000140A5F3EE (0x0000000000D84A20 0x0000000000000000 0x0000000000000000 0x0000000000D20000)
0x0000000140FC922D (0x0000000000B9E5A0 0x0000000000B9DF70 0x0000000000000000 0x00000001425E0104)
0x0000000140F27434 (0x0000000000D20230 0x0000000000D20230 0x0000000000D204A8 0x0000000000D25478)
0x0000000140F2B858 (0x0000000000D20158 0x0000000000000000 0x0000000000000000 0x0000000000000003)
0x000000013F6E3F9D (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x01D4A35EF2AE27A0)
0x000000014258A7E8 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0x00000000776B59CD (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), BaseThreadInitThunk() + 0xD bytes(s)
0x000000007781385D (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), RtlUserThreadStart() + 0x1D bytes(s)
Does anyone have any Idea what could be causing this?
Some things I have tried:
seen somewhere that installing Mingw might help. Didnt make a difference.
Removed everything from path other than the c:\clang directory
Moved a test file to the clang directory and still same result.
figured out that running clang with no arguments. same result.
Ran as Administrator
I suspect that there is a missing runtime dll or file, but shouldnt a clean install have installed all the needed files?
Also i have 4 GB memory (1.5 used by system) with a quad core cpu so i doubt its running out of actual memory on startup.
EDIT: Im starting to narrow in on this problem. Ive literally spent a week now trying to get clang to start on my windows 7 machine. Ive downloaded and installed every vc redist, installed numerous updates and KB fixes. Still nothing. Using dependancy walker ive discovered that clang fails to load DLL files from the WINRT api set.Specifically the whole "API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL" not found- family of problems. Ive coppied all 41 dlls from the win 10 redist folder in the win 10 sdk over to the clang folder and still no joy. will i not be able to run clang on windows 7?
EDIT 2: For anyone coming here with the same problem ive discovered the problem and it is deep. Apparently Clang/LLVM for Windows is compiled by (or compiled against libraries in) Visual Studio. Really Clang...? Why cant you compile your compiler with your own compiler? Eat your own dog food as they say. That being said, i discovered this by installing a debug build of llvm which gave me some better error diagnoatics. Following the error codes down the deep google rabbit hole brought me to the mailing list for llvm from 2 years ago where they discussed this problem and also discussed moving compilation from VS 2013 to VS 2015. The problem is that compiling with VS (Visual Studio) creates a dependancy on the 64 bit DIA (Debug Interface Access) dll which is only installed on systems with visual studio installed (and on Windows 10 apparently). Thats why it wasnt working on my system, I had installed clang for the very reason that I didnt want to install the monster 10 gigabyte Visual STudio on my computer. However, after discovering this I relinquished my stubborness and installed it. Boom! Clang works like a charm.
Related
Please suggest registry entry of delphi XE help system as it is pointing to wrong drive due and not opening in ide as my hard drive partition no longer exists where it was installed previously.even re-installation not working as it is asking for remove
So I have Delphi XE (no number) and I have a project that was built on another machine (using JVCL components). Now, my machine is a Windows 8.1 (64 bits), and the previous machine was Windows XP (32 bits).
Of course I want to be able to continue developing the app, but for that I need the JCL/JVCL to be installed here too.
Now comes my problem. When I run the installer (bat) of JCL, it starts ok, but it does not show any options, so when I click the Install button nothing happens, and I get a message saying the installation finished. But of course nothing is installed.
This is how the installer looks on my x64 machine:
What can I do to install this JCL on a win64 machine? I am very sure that this is the problem: the OS. Because on 32bit OS (Windows XP) I have no problem installing it.
I looked it up, but could not find a straightforward solution. There might be a problem with some registry where the installer looks for the location of Delphi ?!?! but I have no idea how to fix it.
I need to install the JVCL, but it wont install unless I have JCL installed first... and the JCL does not install
Please help me.
Thank you
I want to run an .NET executable that needs more than 4G RAM on OSX 10.9. I had Xamarin Studio installed but AFAIKT Xamarin doesn't come with a 64-bit mono build, so I decided to make a custom 64-bit mono with "with-large-heap=yes" configuration, and install it in a different location.
git clone https://github.com/mono/mono
cd mono
./configure --prefix=<my-local-dir> --enable-nls=no --with-large-heap=yes
make
make install
(I also built a 64-bit F# and installed in my-local-dir, following "Option 3" in this page.)
However, when I use the 64-bit mono to run the executable (an F# program built with the canonical "fsharpc" in Xamarin), it still crashes with System.OuOtfMemory exception. I tried this:
export PATH=$PATH:<my-local-dir>/bin
MONO_GC_PARAMS=max-heap-size=5g <my-local-dir>/bin/mono <my-executable>
And it gives a warning
Warning: In environment variable `MONO_GC_PARAMS': `max-heap-size` must be an integer.
(this error message is a bit misleading, I think it really means 5g is too large and not supported, because it doesn't complain if I put a "3g" there). And the program still crash with the same exception at the point when it exceeds the memory.
Did I miss any thing important? How do I configure mono to have more than 4G heap size?
You are still running the 32 bit version of mono (check your PATH env var). This also explains the parsing of 5g for max-heap-size (it will work correctly with 64 bit mono).
The default as with your configure command above is to install in /usr/local/bin, so just run your programs with /usr/local/bin/mono program.exe.
I search for a solution.
We have Delphi 6 Prof on Win7/X64.
When I tried four times to install JCL, the Windows crash with Blue Death.
I set the installer.exe to "Windows XP mode" but nothing happens.
How can I install JCL to my Delphi, and what CAN cause full crash in Win7?
Thanks:
dd
Most likely this is a hardware fault. Run diagnostics on your disk. Hope that your backup works!
I installed both the Delphi 2009 trial and actual release via the web installer when I received them and experienced the same errors when installing both.
Both times it appears that the core web installer failed when it went to spawn the additional install packages for boost, documentation and dbtools. (It brought up a findfile dialog asking for a setup.msi that didn't exist on my machine). When cancelling out of this, the installer reported a fatal error.
The uninstaller did not appear in my program list, and would did not launch from the installation folder.
Future attempts to bring up the installer had it in a state where it thought Delphi 2009 was already installed and it wouldn't correct or repair or uninstall it.
Step 1
Clean out the registry of all things Delphi 2009.
You're looking for HKLM\Software\Codegear\BDS\6.0 and everything under it. Purge the HKCU equivalent while you're at it.
Search under HKEY.CLASSES.ROOT for anything that contains "CodeGear\RAD Studio\6.0" - assuming you installed into the default folder. Purge all those items from the CLSID level.
Step 2
Clean up Windows Installer using the Microsoft Windows Installer Cleanup utility.
Step 3
I suggest a reboot at this stage.
Step 4
Try to install again.
Good Luck!
The problems seem to originate with the web installer not having all the files needed.
Download the 2009 ISO: http://cc.codegear.com/item/26049
Mounted it using this free tool from Microsoft: http://download.microsoft.com/download/7/b/6/7b6abd84-7841-4978-96f5-bd58df02efa2/winxpvirtualcdcontrolpanel_21.exe (You can burn it to a DVD too)
Then reran the installer. At this point, both the repair and uninstall worked.