|How to identify compilers firstname.lastname@example.org (2003-01-30)|
|Re: How to identify compilers email@example.com (Joachim Durchholz) (2003-02-05)|
|Re: How to identify compilers firstname.lastname@example.org (David Chase) (2003-02-05)|
|Re: How to identify compilers email@example.com (Ron Ruble) (2003-02-05)|
|Re: How to identify compilers firstname.lastname@example.org (2003-02-06)|
|Re: How to identify compilers email@example.com (2003-02-06)|
|Re: How to identify compilers firstname.lastname@example.org (Allan Sandfeld Jensen) (2003-02-11)|
|Re: How to identify compilers email@example.com (Alex K. Angelopoulos) (2003-02-21)|
|Re: How to identify compilers firstname.lastname@example.org (2003-02-24)|
|From:||"Ron Ruble" <email@example.com>|
|Date:||5 Feb 2003 23:58:41 -0500|
|Organization:||Posted via Supernews, http://www.supernews.com|
|Posted-Date:||05 Feb 2003 23:58:41 EST|
"Robert" <firstname.lastname@example.org> wrote
> Did anybody know, if (and how) it's possible to find out with which
> compiler a Windows executable file was compiled.
Not reliably. The program may link in specific DLLs, which may give a
clue, or the code may otherwise have certain artifacts peculiar to one
particular compiler, but there is no general way to discover this.
Most, if not all, potential identifying information was removed as
part of the compilation process.
Of course, this begs the question "why do you want to know?"
Return to the
Search the comp.compilers archives again.