Skip to content
Snippets Groups Projects
Commit bdfce4ad authored by Joakim Bech's avatar Joakim Bech Committed by Joakim Bech
Browse files

docs: update debug.md to match the new trace output 


Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
Reviewed-by: default avatarEtienne Carriere <etienne.carriere@linaro.org>
parent da5f891e
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 81 additions and 77 deletions
docs/debug.md
+ 81
− 77
View file @ bdfce4ad
......@@ -415,107 +415,111 @@ $ echo 0 > options/graph-time
When OP-TEE encounters a serious error condition, it prints diagnostic
information to the secure console. The message contains a call stack if
CFG_UNWIND=y (enabled by default).
`CFG_UNWIND=y` (enabled by default).
The following errors will trigger a dump:
- Data or prefetch abort exception in the TEE core (kernel mode) or in a TA
(user mode),
- When a user-mode Trusted Application panics, either by calling TEE_Panic()
directly or due to some error detected by the TEE Core Internal API,
(user mode),
- When a user-mode Trusted Application panics, either by calling `TEE_Panic()`
directly or due to some error detected by the TEE Core Internal API,
- When the TEE core detects a fatal error and decides to hang the system
because there is no way to proceed safely (core panic).
because there is no way to proceed safely (core panic).
The messages look slightly different depending on:
- Whether the error is an exception or a panic,
- The exception/privilege level when the exception occurred (PL0/EL0 if a
user mode Trusted Application was running, PL1/EL1 if it was the TEE core),
user mode Trusted Application was running, PL1/EL1 if it was the TEE core),
- Whether the TEE and TA are 32 or 64 bits,
- The exact type of exception (data or prefetch abort, translation fault,
read or write permission fault).
Here is an example of a data abort with write permission fault in a 32-bit
Trusted Application, running on a 32-bit TEE core (QEMU):
```
ERROR: [0x0] TEE-CORE: User TA data-abort at address 0x131658 (write permission fault)
ERROR: [0x0] TEE-CORE: fsr 0x0000080f ttbr0 0x0e07a06a ttbr1 0x0e07406a cidr 0x1
ERROR: [0x0] TEE-CORE: cpu #0 cpsr 0x20000030
ERROR: [0x0] TEE-CORE: r0 0x0012937f r4 0x0013a0e4 r8 0x00000000 r12 0x0e07dd80
ERROR: [0x0] TEE-CORE: r1 0x00001b00 r5 0x00121e47 r9 0x00000000 sp 0x001026f4
ERROR: [0x0] TEE-CORE: r2 0x00131658 r6 0x001026f4 r10 0x00000000 lr 0x00121bc9
ERROR: [0x0] TEE-CORE: r3 0x00000002 r7 0x001026f4 r11 0x00000000 pc 0x00105bdc
ERROR: [0x0] TEE-CORE: Status of TA 5b9e0e40-2636-11e1-ad9e-0002a5d5c51b (0xe073b70) (active)
ERROR: [0x0] TEE-CORE: arch: arm load address: 0x103000 ctx-idr: 1
ERROR: [0x0] TEE-CORE: stack: 0x100000 10240
ERROR: [0x0] TEE-CORE: region 0: va 0x100000 pa 0xe31e000 size 0x3000 flags rw-
ERROR: [0x0] TEE-CORE: region 1: va 0x103000 pa 0xe200000 size 0x2e000 flags r-x
ERROR: [0x0] TEE-CORE: region 2: va 0x131000 pa 0xe22e000 size 0xa000 flags r--
ERROR: [0x0] TEE-CORE: region 3: va 0x13b000 pa 0xe238000 size 0xe6000 flags rw-
ERROR: [0x0] TEE-CORE: region 4: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 5: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 6: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 7: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: Call stack:
ERROR: [0x0] TEE-CORE: 0x00105bdc
ERROR: [0x0] TEE-CORE: 0x00121bc9
ERROR: [0x0] TEE-CORE: 0x00121d1b
ERROR: [0x0] TEE-CORE: 0x00121e6f
```
The above dump was triggered by the TA trying to write to a global const
variable. Such variables are stored in the `.rodata` section of the ELF binary,
and loaded into a read-only section of memory.
OP-TEE provides a helper script called `symbolize.py` to facilitate the
analysis of such issues. It is located in the OP-TEE OS source tree, and is
also copied to the TA development kit. Whenever you are confronted with an error
message reporting a serious error and showing a "Call stack:" line, you may use
the symbolize script.
read or write permission fault, alignment errors etc).
Here is an example of a panic in a 32-bit Trusted Application, running on a
32-bit TEE core (QEMU):
```
E/TC:0 TA panicked with code 0x0
E/TC:0 Status of TA 484d4143-2d53-4841-3120-4a6f636b6542 (0xe07ba50) (active)
E/TC:0 arch: arm load address: 0x101000 ctx-idr: 1
E/TC:0 stack: 0x100000 4096
E/TC:0 region 0: va 0x100000 pa 0xe31d000 size 0x1000 flags rw-
E/TC:0 region 1: va 0x101000 pa 0xe300000 size 0xf000 flags r-x
E/TC:0 region 2: va 0x110000 pa 0xe30f000 size 0x3000 flags r--
E/TC:0 region 3: va 0x113000 pa 0xe312000 size 0xb000 flags rw-
E/TC:0 region 4: va 0 pa 0 size 0 flags ---
E/TC:0 region 5: va 0 pa 0 size 0 flags ---
E/TC:0 region 6: va 0 pa 0 size 0 flags ---
E/TC:0 region 7: va 0 pa 0 size 0 flags ---
E/TC:0 Call stack:
E/TC:0 0x001044a8
E/TC:0 0x0010ba59
E/TC:0 0x00101093
E/TC:0 0x001013ed
E/TC:0 0x00101545
E/TC:0 0x0010441b
E/TC:0 0x00104477
D/TC:0 user_ta_enter:452 tee_user_ta_enter: TA panicked with code 0x0
D/TC:0 tee_ta_invoke_command:649 Error: ffff3024 of 3
D/TC:0 tee_ta_close_session:402 tee_ta_close_session(0xe07be98)
D/TC:0 tee_ta_close_session:421 Destroy session
D/TC:0 tee_ta_close_session:447 Destroy TA ctx
```
The above dump was triggered by the TA when entering an irrecoverable error
ending up in a `TEE_Panic(0)` call.
OP-TEE provides a helper script called `symbolize.py` to facilitate the analysis
of such issues. It is located in the OP-TEE OS source tree, and is also copied
to the TA development kit. Whenever you are confronted with an error message
reporting a serious error and showing a `"Call stack:"` line, you may use the
symbolize script.
`symbolize.py` reads its input from stdin and writes extended debug information
to stdout. The `-d` (directories) option tells the script where to look for TA
ELF file(s) or for `tee.elf` (the TEE core). The `-s` (strip) option is used
to shorten the source file paths. Please refer to `symbolize.py --help` for
ELF file(s) or for `tee.elf` (the TEE core). The `-s` (strip) option is used to
shorten the source file paths. Please refer to `symbolize.py --help` for
details.
```
$ cat dump.txt | ./optee_os/scripts/symbolize.py -d optee_test/out/ta/* -d optee_os/out/arm/core -s `pwd`
$ cat dump.txt | ./optee_os/scripts/symbolize.py -d ./optee_examples/*/ta -s `pwd`
# (or run the script, copy and paste the dump, then press Ctrl+D)
ERROR: [0x0] TEE-CORE: User TA data-abort at address 0x131658 (write permission fault)
ERROR: [0x0] TEE-CORE: fsr 0x0000080f ttbr0 0x0e07a06a ttbr1 0x0e07406a cidr 0x1
ERROR: [0x0] TEE-CORE: cpu #0 cpsr 0x20000030
ERROR: [0x0] TEE-CORE: r0 0x0012937f r4 0x0013a0e4 r8 0x00000000 r12 0x0e07dd80
ERROR: [0x0] TEE-CORE: r1 0x00001b00 r5 0x00121e47 r9 0x00000000 sp 0x001026f4
ERROR: [0x0] TEE-CORE: r2 0x00131658 r6 0x001026f4 r10 0x00000000 lr 0x00121bc9
ERROR: [0x0] TEE-CORE: r3 0x00000002 r7 0x001026f4 r11 0x00000000 pc 0x00105bdc
ERROR: [0x0] TEE-CORE: Status of TA 5b9e0e40-2636-11e1-ad9e-0002a5d5c51b (0xe073b70) (active)
ERROR: [0x0] TEE-CORE: arch: arm load address: 0x103000 ctx-idr: 1
ERROR: [0x0] TEE-CORE: stack: 0x100000 10240
ERROR: [0x0] TEE-CORE: region 0: va 0x100000 pa 0xe31e000 size 0x3000 flags rw-
ERROR: [0x0] TEE-CORE: region 1: va 0x103000 pa 0xe200000 size 0x2e000 flags r-x .ta_head .text .rodata
ERROR: [0x0] TEE-CORE: region 2: va 0x131000 pa 0xe22e000 size 0xa000 flags r-- .rodata .ARM.extab .ARM.extab.text.__aeabi_ldivmod .ARM.extab.text.__aeabi_uldivmod .ARM.exidx .got .dynsym .rel.got .dynamic .dynstr .hash .rel.dyn
ERROR: [0x0] TEE-CORE: region 3: va 0x13b000 pa 0xe238000 size 0xe6000 flags rw- .data .bss
ERROR: [0x0] TEE-CORE: region 4: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 5: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 6: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: region 7: va 0 pa 0 size 0 flags ---
ERROR: [0x0] TEE-CORE: User TA data-abort at address 0x131658 const_var .rodata+4852 (write permission fault)
ERROR: [0x0] TEE-CORE: Call stack:
ERROR: [0x0] TEE-CORE: 0x00105bdc TA_CreateEntryPoint at optee_test/ta/os_test/ta_entry.c:44
ERROR: [0x0] TEE-CORE: 0x00121bc9 ta_header_add_session at optee_os/lib/libutee/arch/arm/user_ta_entry.c:115
ERROR: [0x0] TEE-CORE: 0x00121d1b entry_open_session at optee_os/lib/libutee/arch/arm/user_ta_entry.c:159
ERROR: [0x0] TEE-CORE: 0x00121e6f __utee_entry at optee_os/lib/libutee/arch/arm/user_ta_entry.c:229
E/TC:0 TA panicked with code 0x0
E/TC:0 Status of TA 484d4143-2d53-4841-3120-4a6f636b6542 (0xe07ba50) (active)
E/TC:0 arch: arm load address: 0x101000 ctx-idr: 1
E/TC:0 stack: 0x100000 4096
E/TC:0 region 0: va 0x100000 pa 0xe31d000 size 0x1000 flags rw-
E/TC:0 region 1: va 0x101000 pa 0xe300000 size 0xf000 flags r-x .ta_head .text .rodata
E/TC:0 region 2: va 0x110000 pa 0xe30f000 size 0x3000 flags r-- .rodata .ARM.extab .ARM.extab.text.utee_panic .ARM.extab.text.__aeabi_ldivmod .ARM.extab.text.__aeabi_uldivmod .ARM.exidx .got .dynsym .rel.got .dynamic .dynstr .hash .rel.dyn
E/TC:0 region 3: va 0x113000 pa 0xe312000 size 0xb000 flags rw- .data .bss
E/TC:0 region 4: va 0 pa 0 size 0 flags ---
E/TC:0 region 5: va 0 pa 0 size 0 flags ---
E/TC:0 region 6: va 0 pa 0 size 0 flags ---
E/TC:0 region 7: va 0 pa 0 size 0 flags ---
E/TC:0 Call stack:
E/TC:0 0x001044a8 utee_panic at optee_os/lib/libutee/arch/arm/utee_syscalls_a32.S:74
E/TC:0 0x0010ba59 TEE_Panic at optee_os/lib/libutee/tee_api_panic.c:35
E/TC:0 0x00101093 hmac_sha1 at optee_examples/hotp/ta/hotp_ta.c:63
E/TC:0 0x001013ed get_hotp at optee_examples/hotp/ta/hotp_ta.c:171
E/TC:0 0x00101545 TA_InvokeCommandEntryPoint at optee_examples/hotp/ta/hotp_ta.c:225
E/TC:0 0x0010441b entry_invoke_command at optee_os/lib/libutee/arch/arm/user_ta_entry.c:207
E/TC:0 0x00104477 __utee_entry at optee_os/lib/libutee/arch/arm/user_ta_entry.c:235
D/TC:0 user_ta_enter:452 tee_user_ta_enter: TA panicked with code 0x0 ???
D/TC:0 tee_ta_invoke_command:649 Error: ffff3024 of 3
D/TC:0 tee_ta_close_session:402 tee_ta_close_session(0xe07be98)
D/TC:0 tee_ta_close_session:421 Destroy session
D/TC:0 tee_ta_close_session:447 Destroy TA ctx
```
The Python script uses several tools from the GNU Binutils package to perform
the following tasks:
1. Translate the call stack addresses into function names, file names and line
numbers;
2. Convert the abort address to a symbol plus some offset (`const_var` in the
example) and/or an ELF section name plus some offset (`.rodata+4852` in the
example);
numbers.
2. Convert the abort address to a symbol plus some offset and/or an ELF section
name plus some offset.
3. Print the names of the ELF sections contained in each memory region of a TA.
Note that to successfully run `symbolize.py` you must also make your toolchain
visible on the `PATH` (i.e., `export PATH=<my-toolchain-path>/bin:$PATH`).
[Affinic Debugger]: http://www.affinic.com/?page_id=109
[README.md]: ../README.md
[QEMU ARMv7-A]: qemu.md#3-qemu-console
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Datenschutz und Impressum