| Related articles |
|---|
| [2 earlier articles] |
| 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) |
| From: | cyberguijarro@terra.es (Emilio Guijarro Cameros) |
| Newsgroups: | comp.compilers |
| Date: | 24 Feb 2003 18:02:09 -0500 |
| Organization: | http://groups.google.com/ |
| References: | 03-01-184 |
| Keywords: | practice |
| 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:
Library functions
Calling conventions
Functions calling overhead
Standard entry-point routines
Executable secions naming
RTTI info
Runtime libraries
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.
http://www.fileinspector.cjb.net
Return to the
comp.compilers page.
Search the
comp.compilers archives again.