Internal compiler error for clang-cl testing Boost config

I received an internal compiler error for clang-cl when testing clang-cl with Boost config. How do I generate a crash backtrace and anything else that is needed for a bug report.

Stack dump:
0. Program arguments: C:\Programming\VersionControl\bclang\bin\Release\clang-cl.exe -cc1 -triple i686-pc-win32 -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name config_test.cpp -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -target-cpu pentium4 -D_DEBUG -D_MT -D_DLL --dependent-lib=msvcrtd --dependent-lib=oldnames -cxx-abi microsoft -fdiagnostics-format msvc -coverage-file C:\Programming\VersionControl\modular-boost\libs\config\test\..\..\..\bin.v2\libs\config\test\config_test_threaded.test\clang-vc11-win-3.4\debug\threading-multi\config_test.obj -resource-dir C:\Programming\VersionControl\bclang\bin\Release\..\lib\clang\3.5 -D _HAS_EXCEPTIONS=0 -D BOOST_ALL_NO_LIB=1 -I ..\..\.. -internal-isystem C:\Programming\VersionControl\bclang\bin\Release\..\lib\clang\3.5\include -internal-isystem C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\INCLUDE -internal-isystem C:\Program Files (x86)\Microsoft Visu!

al Studi
o 11.0\VC\ATLMFC\INCLUDE -internal-isystem C:\Program Files (x86)\Windows Kits\8.0\include\shared -internal-isystem C:\Program Files (x86)\Windows Kits\8.0\include\um -internal-isystem C:\Program Files (x86)\Windows Kits\8.0\include\winrt -O0 -Wall -std=c++11 -fdeprecated-macro -fdebug-compilation-dir C:\Programming\VersionControl\modular-boost\libs\config\test -ferror-limit 19 -fmessage-length 0 -mstackrealign -fno-rtti -fms-extensions -fms-compatibility -fmsc-version=1700 -fdelayed-template-parsing -fno-inline -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -vectorize-slp -o ..\..\..\bin.v2\libs\config\test\config_test_threaded.test\clang-vc11-win-3.4\debug\threading-multi\config_test.obj -x c++ config_test.cpp

The pre-built binaries were built without debug info, so you won’t be able to get a stack trace unfortunately. Going forward we should probably make sure we always generate PDBs for released builds.

In general, the next step would be to generate pre-processed source with -E or /P, but in this case I think I have a repro that I can file.

The pre-built binaries were built without debug info, so you won't be
able to get a stack trace unfortunately. Going forward we should
probably make sure we always generate PDBs for released builds.

Actually I built the binary from source. I was just running the release build, although I could have built a debug build and run that.

In general, the next step would be to generate pre-processed source with
-E or /P, but in this case I think I have a repro that I can file.

If you know what it is about, that's great. If you need it I can try passing the /E or /P to get preprocessed source but it will be pretty big as output since the Boost config test which failed includes many headers.