So, I now only have Visual Studio 2017 on my PC. I removed Visual Studio 2015.
Yet, I have all these folders:
For example:
And for others:
Visual Studio 11.0:
Volume in drive C has no label.
Volume Serial Number is 7810-74A5
Directory of C:\Program Files (x86)\Microsoft Visual Studio 11.0
22/08/2016 14:55 <DIR> .
22/08/2016 14:55 <DIR> ..
22/08/2016 14:55 0 extensions.configurationchanged
05/07/2016 09:33 <DIR> VC
1 File(s) 0 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\UnitTest\WindowsPhone\Include
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
03/08/2015 18:00 19,323 CppUnitTest.h
03/08/2015 18:00 26,741 CppUnitTestAssert.h
03/08/2015 18:00 2,030 CppUnitTestCommon.h
03/08/2015 18:00 384 CppUnitTestException.h
03/08/2015 18:00 1,152 CppUnitTestLogger.h
5 File(s) 49,630 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\UnitTest\WindowsPhone\Lib
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
05/07/2016 09:33 <DIR> arm
11/06/2015 13:41 14,508 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,508 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\UnitTest\WindowsPhone\Lib\arm
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
11/06/2015 13:41 14,508 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,508 bytes
Total Files Listed:
8 File(s) 78,646 bytes
20 Dir(s) 16,162,922,496 bytes free
Visual Studio 12.0:
Volume in drive C has no label.
Volume Serial Number is 7810-74A5
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0
19/09/2016 15:07 <DIR> .
19/09/2016 15:07 <DIR> ..
19/09/2016 15:07 <DIR> Common7
22/08/2016 14:55 0 extensions.configurationchanged
05/07/2016 09:33 <DIR> VC
1 File(s) 0 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger
19/09/2016 15:07 <DIR> .
19/09/2016 15:07 <DIR> ..
10/10/2015 21:34 895,648 msdia120.dll
1 File(s) 895,648 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\Include
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
20/09/2015 16:20 19,323 CppUnitTest.h
20/09/2015 16:20 26,741 CppUnitTestAssert.h
20/09/2015 16:20 2,030 CppUnitTestCommon.h
20/09/2015 16:20 384 CppUnitTestException.h
20/09/2015 16:20 1,152 CppUnitTestLogger.h
5 File(s) 49,630 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\Lib
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
05/07/2016 09:33 <DIR> amd64
05/07/2016 09:33 <DIR> arm
20/06/2016 13:04 14,508 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,508 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\Lib\amd64
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
20/06/2016 12:33 14,786 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,786 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\Lib\arm
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
20/06/2016 12:17 14,636 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,636 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\WindowsPhone\Include
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
03/08/2015 18:00 19,323 CppUnitTest.h
03/08/2015 18:00 26,741 CppUnitTestAssert.h
03/08/2015 18:00 2,030 CppUnitTestCommon.h
03/08/2015 18:00 384 CppUnitTestException.h
03/08/2015 18:00 1,152 CppUnitTestLogger.h
5 File(s) 49,630 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\WindowsPhone\Lib
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
05/07/2016 09:33 <DIR> arm
20/06/2016 13:04 14,508 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,508 bytes
Directory of C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\UnitTest\WindowsPhone\Lib\arm
05/07/2016 09:33 <DIR> .
05/07/2016 09:33 <DIR> ..
20/06/2016 12:17 14,508 Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib
1 File(s) 14,508 bytes
Total Files Listed:
17 File(s) 1,067,854 bytes
41 Dir(s) 16,162,332,672 bytes free
The 14.0 folder has over 3 GB of data in it.
The .Old folder has about 15 MB of data in it.
Visual Studio 2017 is installed in:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
I just seem to have a lot of files here and appreciate some advice.
Thank you.
Update
Looking here:
So we have 2 files from Visual Studio 2005 which I have never installed (in years).
We have a handful of files from Visual Studio 2012 which I have never owned.
We have a few files from Visual Studio 2013. Now, I did own that (paid for it).
Then, despite the fact I uninstalled VS2015 there are GB's of data still there and no actual executable.
I think the .old folder is a past attempt at the 2017 version when I had problems before. So I think that is redundant.
Update 2
I thought I would just see what the Control Panel indicated as still installed.
Microsoft Visual Studio 2005:
Microsoft Visual Studio 2008:
Microsoft Visual Studio 2012:
Microsoft Visual Studio 2013:
Microsoft Visual Studio 2015:
Related
Compiling binutils-2.33.1 for ARM64 (aarch64*--).
The build passes but I'm getting strange issues in some programs. GNU MP for example core dumps when building its generator. Handling of long's seem broken.
When I run make check on the binutils-2.33.1 build. There is only 3 unexpected failures. They definitely stands out:
Running /custom_toolchain/binutils-2.33.1/binutils/testsuite/binutils-all/aarch64/aarch64.exp ...
FAIL: Check if disassembler can handle all sections in default order
FAIL: Check if disassembler can handle all sections in different order than header
Running /custom_toolchain/binutils-2.33.1/binutils/testsuite/binutils-all/objdump.exp ...
Version /custom_toolchain/build/binutils/objdump 2.33.1
FAIL: build-id-debuglink (grepping for source file name in disassembly output)
Can I safely ignore these failures? If not, any thought to the cause?
You should not ignore those failures. If you have access to a linux x86_64 system, you could cross-compile binutils 2.33.1 using a toolchain that can be trusted, such as a gcc toolchain from either Linaro or Arm: The root cause may be a defective tool on your Aarch64 system.
A procedure for cross-compiling binutils on a linux x86_64 system would be:
wget https://mirror.csclub.uwaterloo.ca/gnu/binutils/binutils-2.33.1.tar.xz
wget https://releases.linaro.org/components/toolchain/binaries/7.5-2019.12/aarch64-linux-gnu/gcc-linaro-7.5.0-2019.12-i686_aarch64-linux-gnu.tar.xz
tar Jxf binutils-2.33.1.tar.xz
tar Jxf aarch64-linux-gnu/gcc-linaro-7.5.0-2019.12-i686_aarch64-linux-gnu.tar.xz
export CROSS_COMPILE=$(pwd)/gcc-linaro-7.5.0-2019.12-i686_aarch64-linux-gnu/bin/aarch64-linux-gnu-
export PREFIX=$(pwd)/binutils-2.33.1-aarch64-linux-gnu
mkdir binutils
cd binutils
../binutils-2.33.1/configure --host=aarch64-linux-gnu --with-static-standard-libraries --program-prefix=aarch64-linux-gnu- --prefix=${PREFIX}
make all install
cd -
ls -Gg binutils-2.33.1-aarch64-linux-gnu/bin/
total 98316
-rwxr-xr-x 1 5744720 Dec 13 23:41 aarch64-linux-gnu-addr2line
-rwxr-xr-x 2 5926304 Dec 13 23:41 aarch64-linux-gnu-ar
-rwxr-xr-x 2 8713560 Dec 13 23:41 aarch64-linux-gnu-as
-rwxr-xr-x 1 5696976 Dec 13 23:41 aarch64-linux-gnu-c++filt
-rwxr-xr-x 1 108784 Dec 13 23:41 aarch64-linux-gnu-elfedit
-rwxr-xr-x 1 6314920 Dec 13 23:41 aarch64-linux-gnu-gprof
-rwxr-xr-x 4 9739912 Dec 13 23:42 aarch64-linux-gnu-ld
-rwxr-xr-x 4 9739912 Dec 13 23:42 aarch64-linux-gnu-ld.bfd
-rwxr-xr-x 2 5789736 Dec 13 23:41 aarch64-linux-gnu-nm
-rwxr-xr-x 2 6529712 Dec 13 23:41 aarch64-linux-gnu-objcopy
-rwxr-xr-x 2 9437264 Dec 13 23:41 aarch64-linux-gnu-objdump
-rwxr-xr-x 2 5926304 Dec 13 23:41 aarch64-linux-gnu-ranlib
-rwxr-xr-x 2 2980560 Dec 13 23:41 aarch64-linux-gnu-readelf
-rwxr-xr-x 1 5735096 Dec 13 23:41 aarch64-linux-gnu-size
-rwxr-xr-x 1 5732376 Dec 13 23:41 aarch64-linux-gnu-strings
-rwxr-xr-x 2 6529704 Dec 13 23:41 aarch64-linux-gnu-strip
You could then replace copy binutils executables into your target system: if your problem was binutils-related, this may well solve it.
D:\src\distorm-master>py -3.6-32 setup.py install
running install
running build
running custom_build
Compiling with VS150COMNTOOLS: msbuild /p:Configuration=dll /p:Platform=win32
make/win32/distorm.sln
'"C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\Common7\Tools\..\..\vc\vcvarsall.bat"' is not
recognized as an internal or external command,
operable program or batch file.
compilation with VS150COMNTOOLS failed
error: Failed to compile "make/win32/distorm.sln" with any available compiler
That vcvarsall path doesn't exist. I found it somewhere else and set VS150COMNTOOLS path correctly, still doesn't work:
D:\src\distorm-master>set VS150COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
D:\src\distorm-master>set vs
VS150COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
VSCMD_ARG_app_plat=Desktop
VSCMD_ARG_HOST_ARCH=x86
VSCMD_ARG_TGT_ARCH=x86
VSCMD_VER=15.5.2
VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\
D:\src\distorm-master>py -3.6-32 setup.py install
running install
running build
running custom_build
Compiling with VS150COMNTOOLS: msbuild /p:Configuration=dll /p:Platform=win32 make/win32/distorm.sln
The system cannot find the path specified.
compilation with VS150COMNTOOLS failed
error: Failed to compile "make/win32/distorm.sln" with any available compiler
But that path certainly exists:
Directory of C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build
12/17/2017 11:07 PM <DIR> .
12/17/2017 11:07 PM <DIR> ..
12/17/2017 10:36 PM 13 Microsoft.VCRedistVersion.default.txt
12/17/2017 10:36 PM 291 Microsoft.VCToolsVersion.default.props
12/17/2017 10:36 PM 13 Microsoft.VCToolsVersion.default.txt
12/17/2017 10:36 PM 39 vcvars32.bat
12/17/2017 10:36 PM 39 vcvars64.bat
12/17/2017 10:36 PM 9,187 vcvarsall.bat
12/17/2017 10:36 PM 43 vcvarsamd64_x86.bat
12/17/2017 10:36 PM 43 vcvarsx86_amd64.bat
8 File(s) 9,668 bytes
2 Dir(s) 45,319,999,488 bytes free
From the wiki:
As you can see, Python is no longer supported in the compilation
itself.
There is a cdistorm.vcxproj file in the source repo. Try using that.
protobuf 2.5 has been installed (via brew) and is in the path:
$which protoc
/usr/local/opt/protobuf#2.5/bin/protoc
When compiling (caffe) it is not being found: presumably due to library path settings.
ld: library not found for -lprotobuf
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [.build_release/lib/libcaffe.so.1.0.0-rc3] Error 1
Which env vars need to be updated? I am unclear among which combination of
LD_LIBRARY_PATH
DYLD_LIBRARY_PATH
LIBRARY_PATH
were required
Also: is the following path /usr/local/Cellar/protobuf#2.5/2.5.0/lib correct to use?
$ll /usr/local/Cellar/protobuf#2.5/2.5.0/lib
total 12392
-r--r--r-- 1 boescst admin 1120832 Feb 26 2013 libprotoc.a
-r--r--r-- 1 boescst admin 1536576 Feb 26 2013 libprotobuf.a
-r--r--r-- 1 boescst admin 215672 Feb 26 2013 libprotobuf-lite.a
drwxr-xr-x 12 boescst admin 408 Feb 26 2013 .
drwxr-xr-x 4 boescst admin 136 Mar 12 11:46 pkgconfig
-r--r--r-- 1 boescst admin 659108 Mar 12 11:46 libprotoc.dylib
-r--r--r-- 1 boescst admin 659108 Mar 12 11:46 libprotoc.8.dylib
-r--r--r-- 1 boescst admin 930424 Mar 12 11:46 libprotobuf.dylib
-r--r--r-- 1 boescst admin 930424 Mar 12 11:46 libprotobuf.8.dylib
-r--r--r-- 1 boescst admin 138008 Mar 12 11:46 libprotobuf-lite.dylib
-r--r--r-- 1 boescst admin 138008 Mar 12 11:46 libprotobuf-lite.8.dylib
drwxr-xr-x 11 boescst admin 374 Mar 12 11:46 ..
Finally: do I need to make any symbolic links inside that directory - to make the calling program (caffe in my case ) be able to find the libs?
The libraries included are shown in the Makefile as so:
INCLUDE_DIRS += $(BLAS_INCLUDE)
LIBRARY_DIRS += $(BLAS_LIB)
LIBRARY_DIRS += /usr/local/Cellar/protobuf#2.5/2.5.0/lib
LDFLAGS += $(foreach librarydir,$(LIBRARY_DIRS),-L$(librarydir)) $(PKG_CONFIG)
$(foreach library,$(LIBRARIES),-l$(library))
So is there a way to print out these libraries - without resorting to make -d that generates 265K lines?
When the compiler returns the error:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
This indicates that a particular library attempting to be linked is unable to be located. In most cases it's usually a matter of informing the compiler where the library in question actually is. There are several ways to do this, and it depends on the way something is being built. Since you are using a Makefile adding the following environment variable should resolve the issue:
LIBRARY_PATH=/usr/local/Cellar/protobuf#2.5/2.5.0/lib:$LIBRARY_PATH
This adds the libraries location temporarily in the environment so the compiler is able to locate it.
NOTE: In the case LIBRARY_PATH isn't recognized, LIBRARY_DIRS is the correct variable to use.
On CentOS 6.4 64-bit system I am trying to build a 32-bit version of GLIBC (2.18). Using yum I installed a 32-bit version of the GCC library in /lib. I use a directory named GLIBC32 for my build. After trial and research I settled on these options:
--prefix=/usr/local/lib32 --exec-prefix=/usr/local/bin32 --build=i686-pc-linux-gnu CC="gcc -m32" CXX="gxx -m32"
A lot of the build is successful except it seems that SUNRPC components need objects (crt1.o) and libraries being created by the build. If I had the GLIBC library objects SUNRPC wants I wouldn't need to build the library!!!!
*If I stop and copy crt1.o into /lib, then the build complains about libc.so. ANY SUGGESTIONS APPRECIATED. THANKS*
gcc -m32 /home/oracle/tmp/glibc32/sunrpc/cross-rpc_main.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_hout.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_cout.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_parse.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_scan.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_util.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_svcout.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_clntout.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_tblout.o /home/oracle/tmp/glibc32/sunrpc/cross-rpc_sample.o -o /home/oracle/tmp/glibc32/sunrpc/cross-rpcgen
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
make[2]: * [/home/oracle/tmp/glibc32/sunrpc/cross-rpcgen] Error 1
make[2]: Leaving directory /home/oracle/tmp/glibc-2.18/sunrpc'
make[1]: *** [sunrpc/others] Error 2
make[1]: Leaving directory/home/oracle/tmp/glibc-2.18'
make: * [all] Error 2
Here are the contents of /lib
[oracle#qawebtech glibc32]$ ls -l /lib
total 156
drwxr-xr-x. 3 root root 4096 Oct 18 19:53 alsa
lrwxrwxrwx. 1 root root 14 Oct 18 19:53 cpp -> ../usr/bin/cpp
drwxr-xr-x. 3 root root 4096 Oct 18 19:57 crda
drwxr-xr-x. 43 root root 4096 Oct 18 20:21 firmware
drwxr-xr-x. 6 root root 4096 Oct 18 19:56 kbd
-rwxr-xr-x. 1 root root 120672 Feb 21 2013 libgcc_s-4.4.7-20120601.so.1
lrwxrwxrwx. 1 root root 28 Oct 26 00:39 libgcc_s.so.1 -> libgcc_s-4.4.7-20120601.so.1
drwxr-xr-x. 2 root root 4096 Oct 18 19:57 lsb
dr-xr-xr-x. 4 root root 4096 Oct 18 20:20 modules
drwxr-xr-x. 2 root root 4096 Feb 21 2013 security
drwxr-xr-x. 6 root root 4096 Oct 18 19:52 terminfo
drwxr-xr-x. 5 root root 4096 Oct 26 03:49 udev
There is another less painful way to obtain the 32 bit libraries for Centos 6.4. You can download the i386 RPMs from the Centos repository (http://mirror.centos.org). Then use rpm to install them into a new root. Once you have the library files, move them into /lib and your 32 bit app will be able to find them. You might have to manually repair some links. See this link for details about downloading RPMs into a new root.
How to build a chroot jail for Centos
GLIBC is not really set up to be built on an already existing system unless you are cross-compiling.
Environment : Visual Studio 2010 v10.0.31118.1 SP1, Addins : jetBrain,DXCore,VisualSVN Windows 7 (up to date)
Since a long time Visual Studio is really slow, so I tried to see how to reproduce the problem and it's really simple : I add a letter to a file, save and then try to open an other file.
Then Visual Studio freezes for 10sec or more. if I just save or open a file there is no hang at all.
I looked at the processes with ProcEx.exe and I saw that devenv.exe has a lot of I/O.
So with ProcMon I tried to see what was going on, and I saw that visual studio opened every single file of my web site, and every file of the temporary asp.net files folder linked to my website.
So I looked at the stacktrace of every "ReadFile" operation and I get
0 fltmgr.sys fltmgr.sys + 0x2027 0xfffff880010ab027 C:\Windows\system32\drivers\fltmgr.sys
1 fltmgr.sys fltmgr.sys + 0x48ca 0xfffff880010ad8ca C:\Windows\system32\drivers\fltmgr.sys
2 fltmgr.sys fltmgr.sys + 0x222a3 0xfffff880010cb2a3 C:\Windows\system32\drivers\fltmgr.sys
3 ntoskrnl.exe ntoskrnl.exe + 0x373807 0xfffff80002dda807 C:\Windows\system32\ntoskrnl.exe
4 ntoskrnl.exe ntoskrnl.exe + 0x369e84 0xfffff80002dd0e84 C:\Windows\system32\ntoskrnl.exe
5 ntoskrnl.exe ntoskrnl.exe + 0x36ee4d 0xfffff80002dd5e4d C:\Windows\system32\ntoskrnl.exe
6 ntoskrnl.exe ntoskrnl.exe + 0x375917 0xfffff80002ddc917 C:\Windows\system32\ntoskrnl.exe
7 ntoskrnl.exe ntoskrnl.exe + 0x37f520 0xfffff80002de6520 C:\Windows\system32\ntoskrnl.exe
8 ntoskrnl.exe ntoskrnl.exe + 0x6f993 0xfffff80002ad6993 C:\Windows\system32\ntoskrnl.exe
9 ntdll.dll ntdll.dll + 0x502aa 0x76f602aa C:\Windows\SYSTEM32\ntdll.dll
10 wow64.dll wow64.dll + 0x1bfe3 0x74c0bfe3 C:\Windows\SYSTEM32\wow64.dll
11 wow64.dll wow64.dll + 0xcf87 0x74bfcf87 C:\Windows\SYSTEM32\wow64.dll
12 wow64cpu.dll wow64cpu.dll + 0x276d 0x74b8276d C:\Windows\SYSTEM32\wow64cpu.dll
13 wow64.dll wow64.dll + 0xd07e 0x74bfd07e C:\Windows\SYSTEM32\wow64.dll
14 wow64.dll wow64.dll + 0xc549 0x74bfc549 C:\Windows\SYSTEM32\wow64.dll
15 ntdll.dll ntdll.dll + 0x7c367 0x76f8c367 C:\Windows\SYSTEM32\ntdll.dll
16 ntdll.dll ntdll.dll + 0x32e2e 0x76f42e2e C:\Windows\SYSTEM32\ntdll.dll
17 ntdll.dll ntdll.dll + 0x20056 0x77110056 C:\Windows\SysWOW64\ntdll.dll
18 KERNELBASE.dll KERNELBASE.dll + 0x1b616 0x750bb616 C:\Windows\syswow64\KERNELBASE.dll
19 kernel32.dll kernel32.dll + 0x12345 0x74d82345 C:\Windows\syswow64\kernel32.dll
20 cslangsvc.dll TypeReference_Release + 0x36e86 0x535fbe8b C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
21 cslangsvc.dll TypeReference_Release + 0x36ed9 0x535fbede C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
22 cslangsvc.dll LangService_IsPrimaryThread + 0x2167 0x5357633b C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
23 cslangsvc.dll BaseNode_GetBaseOffset + 0x3f1c 0x536a8311 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
24 cslangsvc.dll BaseNode_GetBaseOffset + 0x39c6 0x536a7dbb C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
25 cslangsvc.dll cslangsvc.dll + 0xedd0 0x534fedd0 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
26 cslangsvc.dll LexData_FindFirstPrecedingNonWhiteChar + 0x1a5a 0x5369b229 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
27 cslangsvc.dll cslangsvc.dll + 0x71efc 0x53561efc C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
28 cslangsvc.dll cslangsvc.dll + 0x71df3 0x53561df3 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
29 cslangsvc.dll cslangsvc.dll + 0x72077 0x53562077 C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
30 cslangsvc.dll UsingDirectiveNode_GetName + 0x603c2 0x5366428d C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC#\VCSPackages\cslangsvc.dll
31 kernel32.dll kernel32.dll + 0x13677 0x74d83677 C:\Windows\syswow64\kernel32.dll
32 ntdll.dll ntdll.dll + 0x39d42 0x77129d42 C:\Windows\SysWOW64\ntdll.dll
33 ntdll.dll ntdll.dll + 0x39d15 0x77129d15 C:\Windows\SysWOW64\ntdll.dll
So do you have any guess ?
Thanks
I found the solution : run CCleaner ! it seems that Visual Studio uses a lot the temp folder, and avast antivirus is scanning it every time you open/save a file.
So I couldn't had a filter in avast for the temp folder, so I preferred emptying it.
Please consider downloading the Visual Studio 2010 Diagnostic Tool and sending the results to Microsoft. The tool will collect a variety of performance information that will help the Visual Studio team come up with a solution (if it's an issue with the core product).