diff --git a/scripts/symbolize.py b/scripts/symbolize.py
index 5b136d0..68d9894 100755
--- a/scripts/symbolize.py
+++ b/scripts/symbolize.py
@@ -25,22 +25,25 @@
                        'pa 0x[0-9a-f]+ size (?P<size>0x[0-9a-f]+)')
 
 epilog = '''
-This scripts reads an OP-TEE abort message from stdin and adds debug
-information ('function at file:line') next to each address in the call stack.
-It uses the paths provided on the command line to locate the appropriate ELF
-binary (tee.elf or Trusted Application) and runs arm-linux-gnueabihf-addr2line
-or aarch64-linux-gnu-addr2line to process the addresses.
+This scripts reads an OP-TEE abort or panic message from stdin and adds debug
+information to the output, such as '<function> at <file>:<line>' next to each
+address in the call stack. Any message generated by OP-TEE and containing a
+call stack can in principle be processed by this script. This currently
+includes aborts and panics from the TEE core as well as from any TA.
+The paths provided on the command line are used to locate the appropriate ELF
+binary (tee.elf or Trusted Application). The GNU binutils (addr2line, objdump,
+nm) are used to extract the debug info.
 
-OP-TEE abort messages are sent to the secure console. They look like the
-following:
+OP-TEE abort and panic messages are sent to the secure console. They look like
+the following:
 
-  ERROR:   TEE-CORE: User TA data-abort at address 0xffffdecd (alignment fault)
+  E/TC:0 User TA data-abort at address 0xffffdecd (alignment fault)
   ...
-  ERROR:   TEE-CORE: Call stack:
-  ERROR:   TEE-CORE:  0x4000549e
-  ERROR:   TEE-CORE:  0x40001f4b
-  ERROR:   TEE-CORE:  0x4000273f
-  ERROR:   TEE-CORE:  0x40005da7
+  E/TC:0 Call stack:
+  E/TC:0  0x4000549e
+  E/TC:0  0x40001f4b
+  E/TC:0  0x4000273f
+  E/TC:0  0x40005da7
 
 Inspired by a script of the same name by the Chromium project.