summaryrefslogtreecommitdiffstats
path: root/chrome/app/nacl_fork_delegate_linux.cc
Commit message (Collapse)AuthorAgeFilesLines
* Tighten up DEPS some more. NaCl/service process code are including internal ↵jam@chromium.org2012-06-041-1/+1
| | | | | | | | | content files. Fix the instances other sandbox stuff, which I'll do in a followup. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/10512010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140346 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove base::environment_vector and ↵thestig@chromium.org2012-02-241-2/+4
| | | | | | | | | | | base::file_handle_mapping_vector to StudlyCaps. BUG=none TEST=none Review URL: http://codereview.chromium.org/9429039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123438 0039d316-1c4b-4281-b951-d872f2087c98
* Maximize RLIMIT_AS resource limit in nacl_helper child before execmcgrathr@chromium.org2011-11-151-0/+12
| | | | | | | | | | | | | | | | | | | | | | NaCl processes need an unusually large amount of address space, because they do huge PROT_NONE mappings to reserve contiguous regions much larger than the memory that will actually be used. An ambient RLIMIT_AS setting can break this, so we need to raise the soft limit to the hard limit (which is usually unlimited). We cannot rely on doing this inside the nacl_helper child itself, so we must do it in the zygote before it exec's nacl_helper_bootstrap. That exec itself could fail if the limit is too small, because nacl_helper_bootstrap uses ELF program headers to reserve a large region of address space. BUG= http://code.google.com/p/nativeclient/issues/detail?id=2438 TEST= nacl apps work when "ulimit -S -v 5376320" was run before starting chrome R=mark@chromium.org,bsy@google.com,bradchen@google.com Review URL: http://codereview.chromium.org/8528041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110123 0039d316-1c4b-4281-b951-d872f2087c98
* Make nacl_helper easily debuggablemcgrathr@chromium.org2011-11-151-0/+6
| | | | | | | | | | | | | | | | This makes it so that attaching gdb to a nacl_helper process, or using gdb on a core dump from such a process, automatically finds the symbols of the nacl_helper executable and all the shared libraries it uses. The theory of operation and the details are explained in comments in the code. BUG= http://code.google.com/p/chromium/issues/detail?id=103436 TEST= nacl still works, gdb attach on nacl_helper process, or gdb on core file from one, find symbols R=mseaborn@chromium.org,bradchen@google.com Review URL: http://codereview.chromium.org/8491060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110120 0039d316-1c4b-4281-b951-d872f2087c98
* Move ZygoteForkDelegateLinux to content/public/common.jam@chromium.org2011-10-251-0/+150
BUG=98716 Review URL: http://codereview.chromium.org/8381029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107128 0039d316-1c4b-4281-b951-d872f2087c98