Up to higher level directory | |||
Name | Date | Size | |
---|---|---|---|
boot_test.sh | 05-Oct-2017 | 719 | |
cleanup.sh | 05-Oct-2017 | 372 | |
get_initial_items.sh | 05-Oct-2017 | 70 | |
glibc_test_script.sh | 05-Oct-2017 | 1.7K | |
interactive_test.sh | 05-Oct-2017 | 1.1K | |
README | 05-Oct-2017 | 1.2K | |
setup.sh | 05-Oct-2017 | 1.7K | |
switch_to_bad.sh | 05-Oct-2017 | 223 | |
switch_to_good.sh | 05-Oct-2017 | 224 | |
test_script.sh | 05-Oct-2017 | 1.2K | |
test_setup.sh | 05-Oct-2017 | 5.4K | |
testing_test.py | 05-Oct-2017 | 1,010 |
1 This is a set of scripts to use when triaging compiler problem by using 2 the bisecting functionality included in the sysroot_wrapper.hardened. 3 The only script that you need to create for your triaging problem is the 4 test_script.sh (The ones in this directory are here only as an example). 5 6 Before running the binary searcher tool you will need to run the setup script: 7 8 ./sysroot_wrapper/setup.sh ${board} ${remote_ip} ${package} 9 10 This setup script will ensure your $BISECT_DIR is properly populated and 11 generate a common variable script for the convenience of the scripts in 12 ./sysroot_wrapper 13 14 To run the binary searcher tool with these scripts, execute it like this: 15 16 ./binary_search_state.py --get_initial_items=./sysroot_wrapper/get_initial_items.sh --switch_to_good=./sysroot_wrapper/switch_to_good.sh --switch_to_bad=./sysroot_wrapper/switch_to_bad.sh --test_script=./sysroot_wrapper/test_script.sh --noincremental --file_args 2>&1 | tee /tmp/binary_search.log 17 18 Finally once done you will want to run the cleanup script: 19 20 ./sysroot_wrapper/cleanup.sh 21 22 For more information on how to use the sysroot_wrapper to do object file 23 triaging see: 24 25 https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/bisecting-compiler-problems 26 27 28 29