[EMAIL PROTECTED] wrote: > >Does executable mean just "program" or does this include "shared > >library", too ? Can I use "usr/src/cmd/mapfile_noexdata" to mark the > >library data segments of my shared librarie(s) as non-executable ? If > >"yes" - why isn't this the default ? > > The SPARC ABI defines all segments as executable; the SPARCv9 ABI > defines the stack as non-executable.
Does the SPARCv[789] ABI handle "data segments" seperately ? > >> But we prefer > >> out executables to be that way. > > > >Why aren't (at least) all network-facing application compiled with > >"usr/src/cmd/mapfile_noexdata" ? Just lazyness ? > > Which ones aren't? Uhm... if I read src.opensolaris.org correctly SPARC does not use "mapfile_noexdata" (see http://src.opensolaris.org/source/search?q=mapfile_noexdata&defs=&refs=&path=%2Fonnv&hist=) ... why isn't this enabled globally for all the code in OS/Net (e.g. libraries+executables) ? > It's not about being lazy; Maybe "lazyness" was too strong but somehow this sounds similar to the fate of "-strconst" (e.g. rotting around). > it's about priorities and the development > environment; the mapfile_noexdata wasn't introduced until somewhere in > S10 which made it unusable for some consolidations. Ok... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
