|[2 earlier articles]|
|Re: How to identify compilers email@example.com (David Chase) (2003-02-05)|
|Re: How to identify compilers firstname.lastname@example.org (Ron Ruble) (2003-02-05)|
|Re: How to identify compilers email@example.com (2003-02-06)|
|Re: How to identify compilers firstname.lastname@example.org (2003-02-06)|
|Re: How to identify compilers email@example.com (Allan Sandfeld Jensen) (2003-02-11)|
|Re: How to identify compilers firstname.lastname@example.org (Alex K. Angelopoulos) (2003-02-21)|
|Re: How to identify compilers email@example.com (2003-02-24)|
|From:||firstname.lastname@example.org (Emilio Guijarro Cameros)|
|Date:||24 Feb 2003 18:02:09 -0500|
|Posted-Date:||24 Feb 2003 18:02:09 EST|
Is not an easy task, and you can be sure that it canīt be done using
fixed algorithms... but all compilers let their own signature in the
executables, such as:
Functions calling overhead
Standard entry-point routines
Executable secions naming
And many more...
his task involves a huge database with lots of compiler info, and a
good heuristic engine for fast and reliable scanning.
You can have a look on this tiny program to analise PE-File header
structure and try to recognize most (old) win32 compilers.
Return to the
Search the comp.compilers archives again.