Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incorporate cap_enter in SOAAP model of Capsicum #27

Open
trombonehero opened this issue May 14, 2015 · 0 comments
Open

Incorporate cap_enter in SOAAP model of Capsicum #27

trombonehero opened this issue May 14, 2015 · 0 comments

Comments

@trombonehero
Copy link
Member

It would be nice if SOAAP understood that cap_enter meant "enter a sandbox and never leave it", rather than manually annotating __soaap_sandbox_region_start at the top-level scope. In Chromium, we currently have to annotate renderer_main, whereas it would be much more programmer-friendly to let SOAAP figure things out based on its sandbox model (even though cap_enter is called deep-ish in the call stack).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@trombonehero