Path: utzoo!attcan!uunet!mcvax!ukc!eagle!icdoc!tgould!iwm
From: iwm@asun3.ic.ac.uk (Ian Moor)
Newsgroups: comp.lang.c
Subject: Re: Jumping to data
Message-ID: <IWM.88Sep13103434@asun3.ic.ac.uk>
Date: 13 Sep 88 09:34:40 GMT
References: <5162@hoptoad.uucp> <225800065@uxe.cso.uiuc.edu>
Sender: news@doc.ic.ac.uk
Organization: Dept. of Computing, Imperial College
Lines: 11
Posting-Front-End: GNU Emacs 18.45.3 of Fri Jun 26 1987 on asun3 (berkeley-unix)

execute permission on your files. 
Think of generate executable == setuid root (sort of).

Do your programs actually poke binary opcodes into memory and jump to
them, or do they have structures with pointers to functions ?  I'm
sure that the compiler will allow pointers to functions that it 
knows it has compiled. If you are actually poking code, have you
considered what happens when you have to move to another machine ?
(I am contemplating trying to debug a program with 'asm' statements
scattered through it -- thats bad enough!)