diff options
| author | ivanpe@google.com <ivanpe@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-21 12:41:03 +0000 |
|---|---|---|
| committer | ivanpe@google.com <ivanpe@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-21 12:41:03 +0000 |
| commit | 0d39935ece19c811aa86977b8aa7743138b6a7fd (patch) | |
| tree | f36ce99cc92dd7ee8d7827dc0e77fd4739ef4794 /apps/apps.gypi | |
| parent | 3677a34c42ec44507671dc5096a4cff088fc5c64 (diff) | |
| download | chromium_src-0d39935ece19c811aa86977b8aa7743138b6a7fd.zip chromium_src-0d39935ece19c811aa86977b8aa7743138b6a7fd.tar.gz chromium_src-0d39935ece19c811aa86977b8aa7743138b6a7fd.tar.bz2 | |
Stack trace symbolization for Chrome sandbox processes.
Patching the POSIX implementation of base::debug::StackTrace to properly
symbolize stack traces when used in Chrome sandbox processes. The main
reason symbolization doesn't work today is because sandboxed processes
cannot open proc/self/maps and the object files that contain the symbols.
The proposed solution is to open all necessary files before enabling the
sandbox and then keep their file descriptors around for the duration of
the sandboxed process. This cannot be done in shipping/retail builds
because it has security implications so for the time being this code will
run only in DEBUG builds of Chrome.
Originally, the code review was started under a different account. For
more information take a look at: https://codereview.chromium.org/156043003/
BUG=341966
Review URL: https://codereview.chromium.org/184273012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@258548 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'apps/apps.gypi')
0 files changed, 0 insertions, 0 deletions