v8/tools/linux-tick-processor
mikhail.naganov@gmail.com 792a6652ad Don't try to build d8 from profiler tick processor scripts.
As described in the issue 1532, this may lead to building a 32-bit version over
existing x64-bit. It's better delegate to delegate this task to an user.

R=vitalyr@chromium.org
BUG=1532

Review URL: http://codereview.chromium.org/7309012

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8530 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2011-07-05 05:27:10 +00:00

34 lines
919 B
Bash
Executable File

#!/bin/sh
tools_path=`cd $(dirname "$0");pwd`
if [ ! "$D8_PATH" ]; then
d8_public=`which d8`
if [ -x $d8_public ]; then D8_PATH=$(dirname "$d8_public"); fi
fi
[ "$D8_PATH" ] || D8_PATH=$tools_path/..
d8_exec=$D8_PATH/d8
if [ ! -x $d8_exec ]; then
echo "d8 shell not found in $D8_PATH"
echo "To build, execute 'scons <flags> d8' from the V8 directory"
exit 1
fi
# find the name of the log file to process, it must not start with a dash.
log_file="v8.log"
for arg in "$@"
do
if ! expr "X${arg}" : "^X-" > /dev/null; then
log_file=${arg}
fi
done
# nm spits out 'no symbols found' messages to stderr.
cat $log_file | $d8_exec $tools_path/splaytree.js $tools_path/codemap.js \
$tools_path/csvparser.js $tools_path/consarray.js \
$tools_path/profile.js $tools_path/profile_view.js \
$tools_path/logreader.js $tools_path/tickprocessor.js \
$tools_path/tickprocessor-driver.js -- $@ 2>/dev/null