• Home
  • History
  • Annotate
Name
Date
Size
#Lines
LOC

..--

READMED22-Nov-20231.2 KiB2916

boot_test.shD22-Nov-2023719 234

cleanup.shD22-Nov-2023372 121

get_initial_items.shD22-Nov-202370 62

glibc_test_script.shD22-Nov-20231.7 KiB5024

interactive_test.shD22-Nov-20231.1 KiB3817

interactive_test_host.shD23-Nov-2023822 2610

setup.shD22-Nov-20231.7 KiB7435

switch_to_bad.shD22-Nov-2023223 103

switch_to_good.shD22-Nov-2023224 103

test_script.shD22-Nov-20231.2 KiB3516

test_setup.shD22-Nov-20235.4 KiB167123

test_setup_host.shD23-Nov-20231 KiB3813

testing_test.pyD22-Nov-20231 KiB3827

README

1This is a set of scripts to use when triaging compiler problem by using
2the bisecting functionality included in the sysroot_wrapper.hardened.
3The only script that you need to create for your triaging problem is the
4test_script.sh (The ones in this directory are here only as an example).
5
6Before running the binary searcher tool you will need to run the setup script:
7
8./sysroot_wrapper/setup.sh ${board} ${remote_ip} ${package}
9
10This setup script will ensure your $BISECT_DIR is properly populated and
11generate a common variable script for the convenience of the scripts in
12./sysroot_wrapper
13
14To 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
18Finally once done you will want to run the cleanup script:
19
20./sysroot_wrapper/cleanup.sh
21
22For more information on how to use the sysroot_wrapper to do object file
23triaging see:
24
25https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/team-tools-and-scripts/bisecting-compiler-problems
26
27
28
29