Xref: utzoo comp.unix.programmer:2148 comp.lang.c:40492
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!thyme!kaleb
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.unix.programmer,comp.lang.c
Subject: Re: methods for putting labels into your software?
Message-ID: <1991Jun26.194059.19047@thyme.jpl.nasa.gov>
Date: 26 Jun 91 19:40:59 GMT
References: <1991Jun26.165609.9692@athena.mit.edu> <1991Jun26.192319.26495@cs.utk.edu>
Distribution: usa
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 28

In article  mullens@jamsun.ic.ornl.gov (James A. Mullens) writes:
>In article  mlevin@jade.tufts.edu writes:
>|> 
>|>    I'd like to hear suggestions, or any tricks that the pros out there
>|> know about, for putting some kind of text label or code into your
>|> executable (compiled and linked from C code) so that if anyone were to
>
>How about a static long int initialized to your social security
>number?  To make finding it in a binary file easier you might
>declare a struct with 2 or 3 such unique numbers, but I think most
>people's social security number would be unique enough by itself.
>

How about little-endian vs. big-endian architectures?  What looks like
your SSN on one machine would surely be scrambled on another.  Same
for text strings coded as long ints.  For that matter, how do you go
about locating an arbitrary integer within some binary?  I'll wager I could
find my social security number buried in binaries all over the place.

And lint, or perhaps an ANSI compiler will complain about these variables 
never being used.  What are you writing that requires this level of
"protection"?  Or do you just want to see how "far" your code goes without
you?   
-- 

Kaleb Keithley                               kaleb@thyme.jpl.nasa.gov

No flashy sig. No clever quips. No famous quotes. This space for rent.