Skip to content

Commit

Permalink
chore: fix section argument typo (#3983)
Browse files Browse the repository at this point in the history
  • Loading branch information
bunseokbot authored Nov 4, 2024
1 parent ff126c8 commit d43fcd2
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/tutorial.md
Original file line number Diff line number Diff line change
Expand Up @@ -800,7 +800,7 @@ into the `maps` section as follows:
```
# Replace X.Y.Z with the actual version of eBPF being used.
> clang -I -I .\eBPF-for-Windows.X.Y.Z\build\native\include\ -target bpf -Werror -g -O2 -c maponly.c -o maponly.o
> llvm-objdump -s -section maps maponly.o
> llvm-objdump -s --section maps maponly.o
maponly.o: file format ELF64-BPF
Expand Down Expand Up @@ -832,7 +832,7 @@ int func1()

This program results in the following disassembly:
```
> llvm-objdump -S -section=myprog map.o
> llvm-objdump -S --section=myprog map.o
map.o: file format ELF64-BPF
Expand Down Expand Up @@ -900,7 +900,7 @@ a program is in a section with the ".rel" prefix followed by the
program section name ("myprog" in this example):

```
> llvm-objdump --triple bpf -section=.relmyprog -r map.o
> llvm-objdump --triple bpf --section=.relmyprog -r map.o
map.o: file format ELF64-BPF
Expand All @@ -913,7 +913,7 @@ offset 0x40, but where is that? llvm-objdump and check both gave us
instruction numbers not offsets, but we can see the raw bytes as follows:

```
> llvm-objdump -s -section=myprog map.o
> llvm-objdump -s --section=myprog map.o
map.o: file format ELF64-BPF
Expand Down

0 comments on commit d43fcd2

Please sign in to comment.