Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there any way to detect (or to hide) the compiler that was used to build an executable file?

share|improve this question
up vote 11 down vote accepted

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!

  1. It has a superb GUI and the interface is really intuitive and simple.
  2. Detection rates are amongst the best given by any other identifier.
  3. Special scanning modes for advanced detections of modified and unknown files.
  4. Shell integration, Command line support, Always on top and Drag'n'Drop capabilities.
  5. Multiple file and directory scanning with recursion.
  6. Task viewer and controller.
  7. Plugin Interface with plugins like Generic OEP Finder and Krypto ANALyzer.
  8. Extra scanning techniques used for even better detections.
  9. Heuristic Scanning options.
  10. New PE details, Imports, Exports and TLS viewers
  11. New built in quick disassembler.
  12. New built in hex viewer.
  13. External signature interface which can be updated by the user.
share|improve this answer
"PEiD detects most common [...] compilers for PE files." that's what the readme says - actually it does not tell how to achive that – mbx Aug 18 '11 at 0:42
@Sathya Note, the included link is now dead. – DuckMaestro Dec 5 '12 at 1:06
@DuckMaestro updated witi an alternative link – Sathya Dec 5 '12 at 2:58
If it cannot detect the compiler something like Nothing found [Overlay] * will be shown - which is confusing if you use that tool for the first time. – mbx Nov 17 '14 at 13:30
"The site ahead contains harmful programs" - Google Chrome. Here's a better link. – Ben N Apr 3 at 15:57

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.

Strings is also available for windows as part of cygwin, or as part of the microsoft sysinternals package.

share|improve this answer
It doesn't show me the compiler name only some dll names project – Eduardo Xavier Mar 25 '14 at 12:57

(Old but okay..)

Language 2000 :

share|improve this answer

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.

share|improve this answer
i was wondering if someone or some software can find if the exe was build with a specific compiler edition (Visual Studio 2010 Professional or Enterprise or Express) – Remus Rigo Dec 8 '09 at 22:35
This usually isn't true. The first part of a PE file is the DOS stub which is usually a program that prints something like "This program cannot be run in DOS mode." – lesderid Oct 12 '11 at 13:11

Not free, but IDA Pro has a very nice compiler detection. Not it's main function of course, but a nice extra.

share|improve this answer

You can use "dependency walker" to check what runtime library it links to. MSVCP100 is Microsoft Visual C++ 2010 x86

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .