Re: How to identify compilers

vbdis@aol.com (VBDis)
6 Feb 2003 00:06:31 -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: vbdis@aol.com (VBDis)
Newsgroups: comp.compilers
Date: 6 Feb 2003 00:06:31 -0500
Organization: AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com
References: 03-01-184
Keywords: practice
Posted-Date: 06 Feb 2003 00:06:31 EST

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


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


Several indicators can exist:


Copyright notice of the compiler or libraries,
typical error messages,
non-native code (Java, MSIL, Basic...),
and the runtime library included or referenced (xyz.DLL) in the executable
file.


The first step would be to identify the programming language, then the
compiler. In .NET it's not so easy to find out the language, because
the runtime system is language independent, but even there language
specific constructs can be found in the executables.


DoDi

Post a followup to this message

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