Re: How to identify compilers

jgd@cix.co.uk (John Dallman)
6 Feb 2003 00:02:25 -0500

          From comp.compilers
Related articles
How to identify compilers robert.kahlert@aeg-hausgeraete.de (2003-01-30)
Re: How to identify compilers joachim_d@gmx.de (Joachim Durchholz) (2003-02-05)
Re: How to identify compilers chase@theworld.com (David Chase) (2003-02-05)
Re: How to identify compilers raffles2@att.net (Ron Ruble) (2003-02-05)
Re: How to identify compilers jgd@cix.co.uk (2003-02-06)
Re: How to identify compilers vbdis@aol.com (2003-02-06)
Re: How to identify compilers sandfeld@diku.dk (Allan Sandfeld Jensen) (2003-02-11)
Re: How to identify compilers aka@mvps.org (Alex K. Angelopoulos) (2003-02-21)
Re: How to identify compilers cyberguijarro@terra.es (2003-02-24)
| List of all articles for this month |
From: jgd@cix.co.uk (John Dallman)
Newsgroups: comp.compilers
Date: 6 Feb 2003 00:02:25 -0500
Organization: Nextra UK
References: 03-01-184
Keywords: practice
Posted-Date: 06 Feb 2003 00:02:25 EST

robert.kahlert@aeg-hausgeraete.de (Robert) wrote:


> Did anybody know, if (and how) it's possible to find out with which
> compiler a Windows executable file was compiled.


There's no one foolproof way, but there are ways to get clues if you
have some background in Windows development tools. Use "dumpbin
/imports my.exe" to get the list of functions imported from DLLs. Then
look at the DLLs. If they're, say, Delphi or VB DLLs, you have a large
clue. If there isn't anything that seems language-specific, then it
may well be Visual C++, which is what Windows is largely written in,
and the name of the msvcr*.DLL that's used may give you precise
details.


Hitting the executable with a strings program can also give you clues.


---
John Dallman jgd@cix.co.uk

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.