suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

notes on the hazards of sandbox break propagation

Browse Source 
svn: r14220
This commit is contained in:
Matthew Flatt 2009-03-22 16:42:03 +00:00
parent a61e7b67f9
commit 5514afa4bc
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
collects/scribblings/reference/sandbox.scrbl
View File

@ -411,12 +411,18 @@ collected by sandbox evaluators. Use
@defboolparam[sandbox-propagate-breaks propagate?]{ @defboolparam[sandbox-propagate-breaks propagate?]{
When this boolean parameter is true, breaking while an evaluator is When both this boolean parameter and @scheme[(break-enabled)] are true,
running evaluator propagates the break signal to the sandboxed breaking while an evaluator is
running propagates the break signal to the sandboxed
context. This makes the sandboxed evaluator break, typically, but context. This makes the sandboxed evaluator break, typically, but
beware that sandboxed evaluation can capture and avoid the breaks (so beware that sandboxed evaluation can capture and avoid the breaks (so
if safe execution of code is your goal, make sure you use it with a if safe execution of code is your goal, make sure you use it with a
time limit). The default is @scheme[#t].} time limit). Also, beware that a break may be received after the
evaluator's result, in which case the evaluation result is lost. Finally,
beware that a break may be propagated after an evaluator has produced
a result, so that the break is visible on the next interaction with
the evaluator (or the break is lost if the evaluator is not used
further). The default is @scheme[#t].}
@defparam[sandbox-namespace-specs spec (cons/c (-> namespace?) @defparam[sandbox-namespace-specs spec (cons/c (-> namespace?)