|appending data to an executable binary firstname.lastname@example.org (2000-04-11)|
|Re: appending data to an executable binary email@example.com (2000-04-14)|
|Re: appending data to an executable binary firstname.lastname@example.org (Joachim Durchholz) (2000-04-14)|
|Re: appending data to an executable binary email@example.com (2000-04-15)|
|Date:||11 Apr 2000 14:36:08 -0400|
|Organization:||Deja.com - Before you buy.|
|Keywords:||linker, question, comment|
I would like to place meta data at the end of a binary executable in
order to be able to quickly scan it and verify its attributes and
associations (such as date of build, test results, etc.). Is it
possible in general to append data to the end of an existing
executable binary or will doing that corrupt the binary? I've tried a
quick test with an MS-Windows NT DLL and doing so didn't seem to cause
any adverse effects.
Would this be platform/compiler dependent? Is there
another/better/any way of tagging a binary _after_ it's been created?
I know I could easily compile in the build date, but I would like to
assure the data is at a known place in the binary for access. Also
there is information I would like to add that is only available after
the binary has been created.
The platforms I have available to me are:
Any information and/or pointers to good documentation are appreciated.
[It's platform dependent, but most of the executable formats I can think
of don't mind extra stuff at the end of the file. -John]
Return to the
Search the comp.compilers archives again.