summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_tests.gypi
diff options
context:
space:
mode:
authorvictorw@chromium.org <victorw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-06-11 22:25:06 +0000
committervictorw@chromium.org <victorw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-06-11 22:25:06 +0000
commitd4d1b878fde9f01c21a8e247288d56df1e5382c6 (patch)
tree370e50600417adf231ce21a239c57428da1ae034 /chrome/chrome_tests.gypi
parent97a28e721396d6337d31e7b532fd4066326cfc0d (diff)
downloadchromium_src-d4d1b878fde9f01c21a8e247288d56df1e5382c6.zip
chromium_src-d4d1b878fde9f01c21a8e247288d56df1e5382c6.tar.gz
chromium_src-d4d1b878fde9f01c21a8e247288d56df1e5382c6.tar.bz2
Do not use CRT strcmp function in PEImage.
This is for chromium dev build with MSVCRT dll. On render process dll initialization, sandbox interception agent patches the dlls, calls PEImage::GetProcOrdinal and GetProcOrdinal calls CRT strcmp function. This may happen before MSVCRT dll loads and crash render process. Using a local string compare function in PEImgage fixes the issue. The patch does not add new functionality and GetProcOrdinal is already covered by existing unittests. R=nsylvain,rvargas BUG=46311 TEST=none Review URL: http://codereview.chromium.org/2756008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49598 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
0 files changed, 0 insertions, 0 deletions