Is there any way to detect (or to hide) the compiler that was used to build an executable file?
PEiD is pretty good
PEiD detects most common packers, cryptors and compilers for PE files. It can currently detect more than 600 different signatures in PE files.
PEiD is special in some aspects when compared to other identifiers already out there!
- It has a superb GUI and the interface is really intuitive and simple.
- Detection rates are amongst the best given by any other identifier.
- Special scanning modes for advanced detections of modified and unknown files.
- Shell integration, Command line support, Always on top and Drag'n'Drop capabilities.
- Multiple file and directory scanning with recursion.
- Task viewer and controller.
- Plugin Interface with plugins like Generic OEP Finder and Krypto ANALyzer.
- Extra scanning techniques used for even better detections.
- Heuristic Scanning options.
- New PE details, Imports, Exports and TLS viewers
- New built in quick disassembler.
- New built in hex viewer.
- External signature interface which can be updated by the user.
Try the *nix utility strings. Using
strings -a foo.exe should produce a pile of results. Redirect to a file and examine in your favorite editor. You may see either a line that directly implicates a specific compiler, such as Borland C++ - Copyright 2002 Borland Corporation. You might only be able to find lines that imply a specific compiler was used, such as in an include path or whatever.
(Old but okay..)
Language 2000 : http://farrokhi.net/language
Not free, but IDA Pro has a very nice compiler detection. Not it's main function of course, but a nice extra.
If you can find a way to examine the first dozen or so bytes of the EXE file, in a hex dump with corresponding ASCII characters displayed, they will usually indicate the compiler used.
You can use "dependency walker" to check what runtime library it links to. MSVCP100 is Microsoft Visual C++ 2010 x86