Skip to content

Commit 98e32a5

Browse files
committed
runtc: rename to run-toochain
Names up to two full words are saner and not too long
1 parent 952b6db commit 98e32a5

File tree

2 files changed

+15
-15
lines changed

2 files changed

+15
-15
lines changed

README.adoc

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -877,7 +877,7 @@ so it is close to the failing `0xbf0000cc`.
877877
`readelf`:
878878

879879
....
880-
./runtc readelf -- -s "$(./getvar build_dir)/kernel_modules-1.0/hello.ko"
880+
./run-toolchain readelf -- -s "$(./getvar build_dir)/kernel_modules-1.0/hello.ko"
881881
....
882882

883883
does not give any interesting hits at `cc`, no symbol was placed that far.
@@ -950,7 +950,7 @@ The base address shows on terminal:
950950
Now let's find the offset of `myinit`:
951951

952952
....
953-
./runtc readelf -- \
953+
./run-toolchain readelf -- \
954954
-s "$(./getvar build_dir)/kernel_modules-1.0/fops.ko" | \
955955
grep myinit
956956
....
@@ -1273,7 +1273,7 @@ Cannot access memory at address 0x10604
12731273
We have also double checked the address with:
12741274

12751275
....
1276-
./runtc --arch arm readelf -- \
1276+
./run-toolchain --arch arm readelf -- \
12771277
-s "$(./getvar --arch arm build_dir)/kernel_modules-1.0/fops.ko" | \
12781278
grep main
12791279
....
@@ -1878,7 +1878,7 @@ TODO Can you run arm executables in the aarch64 guest? https://stackoverflow.com
18781878
I've tried:
18791879

18801880
....
1881-
./runtc --arch aarch64 gcc -- -static ~/test/hello_world.c -o data/9p/a.out
1881+
./run-toolchain --arch aarch64 gcc -- -static ~/test/hello_world.c -o data/9p/a.out
18821882
./run --arch aarch64 --eval-busybox '/mnt/9p/a.out'
18831883
....
18841884

@@ -3679,7 +3679,7 @@ vermagic: 4.17.0 SMP mod_unload modversions
36793679
Module information is stored in a special `.modinfo` section of the ELF file:
36803680

36813681
....
3682-
./runtc readelf -- -SW "$(./getvar target_dir)/module_info.ko"
3682+
./run-toolchain readelf -- -SW "$(./getvar target_dir)/module_info.ko"
36833683
....
36843684

36853685
contains:
@@ -3691,7 +3691,7 @@ contains:
36913691
and:
36923692

36933693
....
3694-
./runtc readelf -- -x .modinfo "$(./getvar build_dir)/module_info.ko"
3694+
./run-toolchain readelf -- -x .modinfo "$(./getvar build_dir)/module_info.ko"
36953695
....
36963696

36973697
gives:
@@ -3908,7 +3908,7 @@ as explained at: https://stackoverflow.com/questions/8545931/using-gdb-to-conver
39083908
The exact same thing can be done post mortem with:
39093909

39103910
....
3911-
./runtc gdb -- \
3911+
./run-toolchain gdb -- \
39123912
-batch \
39133913
-ex 'info line *(myinit+0x1d)' \
39143914
"$(./getvar build_dir)/kernel_modules-1.0/panic.ko" \
@@ -5238,7 +5238,7 @@ Meaning of the flags:
52385238
* `vaddr`: first virtual address of a page the belongs to the process. Notably:
52395239
+
52405240
....
5241-
./runtc readelf -- -l "$(./getvar build_dir)/kernel_modules-1.0/user/virt_to_phys_test.out"
5241+
./run-toolchain readelf -- -l "$(./getvar build_dir)/kernel_modules-1.0/user/virt_to_phys_test.out"
52425242
....
52435243
+
52445244
contains:
@@ -5610,7 +5610,7 @@ Notes:
56105610
It can be found from:
56115611
+
56125612
....
5613-
./runtc readelf -- -e "$(./getvar vmlinux)" | grep Entry
5613+
./run-toolchain readelf -- -e "$(./getvar vmlinux)" | grep Entry
56145614
....
56155615
+
56165616
TODO confirm further. If I try to break there with:
@@ -7169,7 +7169,7 @@ The reason this is cool, is that `ls` is not statically compiled, but since we h
71697169
In other words, much cooler than:
71707170

71717171
....
7172-
./runtc --arch arm gcc -- -static ./packages/kernel_modules/user/hello.c
7172+
./run-toolchain --arch arm gcc -- -static ./packages/kernel_modules/user/hello.c
71737173
qemu-arm a.out
71747174
....
71757175

@@ -7220,9 +7220,9 @@ First we try some `-static` sanity checks.
72207220
Works and prints `hello`:
72217221

72227222
....
7223-
./runtc --arch x86_64 gcc -- -static -o x86_64.out ./packages/kernel_modules/user/hello.c
7224-
./runtc --arch arm gcc -- -static -o arm.out ./packages/kernel_modules/user/hello.c
7225-
./runtc --arch aarch64 gcc -- -static -o aarch64.out ./packages/kernel_modules/user/hello.c
7223+
./run-toolchain --arch x86_64 gcc -- -static -o x86_64.out ./packages/kernel_modules/user/hello.c
7224+
./run-toolchain --arch arm gcc -- -static -o arm.out ./packages/kernel_modules/user/hello.c
7225+
./run-toolchain --arch aarch64 gcc -- -static -o aarch64.out ./packages/kernel_modules/user/hello.c
72267226
"$(./getvar --arch x86_64 --gem5 exec)" "$(./getvar gem5_se_file)" -c ./x86_64.out
72277227
"$(./getvar --arch arm --gem5 exec)" "$(./getvar gem5_se_file)" -c ./arm.out
72287228
"$(./getvar --arch aarch64 --gem5 exec)" "$(./getvar gem5_se_file)" -c ./aarch64.out
@@ -7262,7 +7262,7 @@ gem5 user mode:
72627262
....
72637263
make \
72647264
-C "$(./getvar --arch arm build_dir)/dhrystone-2" \
7265-
CC="$(./runtc --arch arm --dry gcc)" \
7265+
CC="$(./run-toolchain --arch arm --dry gcc)" \
72667266
CFLAGS=-static \
72677267
;
72687268
time \

runtc renamed to run-toolchain

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ if args.dry:
4141
else:
4242
sys.exit(common.run_cmd(
4343
[common.get_toolchain_tool(args.tool)] + args.extra_args,
44-
cmd_file=os.path.join(common.run_dir, 'runtc.sh'),
44+
cmd_file=os.path.join(common.run_dir, 'run-toolchain.sh'),
4545
cwd=common.linux_variant_dir,
4646
show_cmd=False,
4747
))

0 commit comments

Comments
 (0)