On Mon, Mar 15, 2010 at 06:44:06PM -0400, Isaac Dupree wrote: > On 03/15/10 05:42, Simon Marlow wrote: >> On 13/03/2010 20:14, Ian Lynagh wrote: >>> Sat Mar 13 07:45:55 PST 2010 Ian Lynagh<ig...@earth.li> >>> * Add a link-time flag to en/disable the RTS options >>> If RTS options are disabled then: >>> * The ghc_rts_opts C code variable is processed as normal >>> * The GHCRTS environment variable is ignored and, if it is defined, a >>> warning is emitted >>> * The +RTS flag gives an error and terminates the program > > Are these sufficient for the security / setuid use case? I think > writing to stderr might cause the program to do something different than > what was intended (and, as a compiler, we have no idea either what the > program or its caller is supposed to be doing). > > I did not successfully find out from Google-ing whether this is > something to be concerned about.
If you find there's still a problem, please give details. The idea of either silently failing, or silently ignoring the options, isn't too appealing, though. Thanks Ian _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
