Translations by Matthias Klose

hash section [%2zu] '%s' invalid sh_entsize

section [%2d] '%s': cannot get symbol name for signature

section [%2d] '%s': entry %d has zero offset to next entry, but sh_info says there are more entries

cannot get program header count: %s

cannot get program header index at offset %zd: %s

%s: INTERNAL ERROR %d (%s): %s

%s: entry size in section %zd `%s' is not what we expect

%s: size of section %zd `%s' is not multiple of entry size

%s: entries (%zd) in section %zd `%s' is too large

Display the symbol table sections

cannot get section [%zd] header: %s

invalid data in sysv.hash section %d

invalid data in sysv.hash64 section %d

invalid data in gnu.hash section %d

%s %#<PRIx64> used with different address sizes

%s %#<PRIx64> used with different offset sizes

[%6tx] <UNUSED GARBAGE IN REST OF SECTION>

[%6tx] <UNUSED GARBAGE> ... %<PRIu64> bytes ...

[%6tx] empty list

<INVALID DATA>

invalid maximum operations per instruction is zero

<INVALID DATA>

%*s*** missing DW_MACINFO_start_file argument at end of section

-p PID should be a positive process id.

Cannot open core file '%s'

-n MAXFRAMES should be 0 or higher.

-e EXEC needs a core given by --core.

-1 needs a thread id given by -p.

One of -p PID or --core COREFILE should be given.

Show stack of process PID

Show stack found in COREFILE

(optional) EXECUTABLE that produced COREFILE

Additionally show frame activation

Additionally try to lookup DWARF debuginfo name for frame address

Additionally show inlined function frames using DWARF debuginfo if available (implies -d)

Additionally show module file information

Additionally show source file information

Show all additional information (activation, debugname, inlines, module and source)

Do not resolve address to function symbol name

Show raw function symbol names, do not try to demangle names

Show module build-id, load address and pc offset

Show the backtrace of only one thread

Show at most MAXFRAMES per thread (default 256, use 0 for unlimited)

Show module memory map with build-id, elf and debug files detected

Print a stack for each thread in a process or core file.Program exits with return code 0 if all frames were shown without any errors. If some frames were shown, but there were some non-fatal errors, possibly causing an incomplete backtrace, the program exits with return code 1. If no frames could be shown, or a fatal error occured the program exits with return code 2. If the program was invoked with bad or missing arguments it will exit with return code 64.

Couldn't show any frames.

Skipping section %zd '%s' data outside file

Remove section headers (not recommended)

%s: no support for stripping archive

cannot get number of phdrs