Closed
Bug 948620
Opened 12 years ago
Closed 11 years ago
Add env variable to disable sandbox at runtime
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.4 S1 (14feb)
People
(Reporter: kang, Assigned: kang)
References
Details
Attachments
(1 file)
1.23 KB,
patch
|
jld
:
review+
|
Details | Diff | Splinter Review |
See also https://bugzilla.mozilla.org/show_bug.cgi?id=928042 for the Windows equivalent.
Per request (:pauljt, :ladamski) we need this for B2G as well, in order to allow devs to help debugging issues.
Most of the implementation is discussed in bug 928042. It is slightly different than the windows code as the B2G sandbox start in 2 places right now, thus both places have to be handled, or the setprocesssandbox function needs to be handled instead (and its at a different place)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → gdestuynder
Assignee | ||
Comment 1•11 years ago
|
||
simple & straight forward.
mainly, reusing the windows mechanism would involve too many changes IMO.
It uses the same environment variable, MOZ_DISABLE_CONTENT_SANDBOX.
to use:
adb shell
stop b2g
export MOZ_DISABLE_CONTENT_SANDBOX=1
/system/bin/b2g.sh
Attachment #8375104 -
Flags: review?(jld)
Updated•11 years ago
|
Attachment #8375104 -
Flags: review?(jld) → review+
Assignee | ||
Comment 2•11 years ago
|
||
Assignee | ||
Comment 3•11 years ago
|
||
Comment 4•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.4 S1 (14feb)
You need to log in
before you can comment on or make changes to this bug.
Description
•