This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: More DG/UX Intel Build info


alex.buell@tahallah.demon.co.uk writes ...
> 
> On 5 May 1999, Andreas Schwab wrote:
> 
> > |> Shouldn't the OS refuse to do a private mapping at a place where it
> > |> already has mapped code?  I.e. return -1 for error?
> > 
> > Why?  The kernel should not keep you from shooting yourself in your
> > foot. :-)
> 
> *Only* if you're root. Ordinary users should not be able to shoot
> themselves. If they can, it's a bug. 

Can we kill this before it gets out of control and everyone posts
their opinion?

Being able to map over existing mappings is the reason MAP_FIXED
exists, and the reason its use is discouraged.  See any reasonable
documentation of mmap() for more information.

-Tim


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]