LLVM-STRINGS(1)
π LLVM-STRINGS(1) β the LLVM girly's guide to llvm-strings
okay so this is llvm-strings(1), straight out of the LLVM manual set β yes bestie, the same LLVM you already know and love π
β¨ NAME β¨
llvm-strings β it prints strings π that's it, that's the whole vibe.
β¨ SYNOPSIS β¨
llvm-strings [options] [input...]
π¦ DESCRIPTION π¦
so llvm-strings is a tool that is intended as a drop-in replacement for GNU's strings π β it goes looking for printable strings inside files and writes them straight out to the standard output stream. iconic behavior honestly.
and what counts as a printable string, you ask? it's literally any sequence of four (by default, okurrr) or more printable ASCII characters β¨. the end of the file terminates the current sequence, and like... any other byte terminates it too. no cap, that's the rule.
here's the part where it's lowkey different from GNU: llvm-strings looks for strings in each input file specified. but unlike GNU strings, it looks in the entire input file β regardless of file format π β instead of restricting the search to certain sections of object files. main character energy: it reads the whole thing.
and if - is specified as an input, or if you specify no input at all? it reads from the standard input stream π«Ά easy.
πΈ EXAMPLE πΈ
$ cat input.txt
bars
foo
wibble blob
$ llvm-strings input.txt
bars
wibble blob
see how foo didn't make it? only three chars bestie, the vibe check said no π (four is the minimum, remember!)
π OPTIONS π
--all,-aβ silently ignored. it's just there for GNUstringscompatibility, so like... it does nothing, it's decorative, it's an accessory π--bytes=<length>,-nβ sets the minimum number of printable ASCII characters required for a sequence of bytes to count as a string β¨. the default value is4.--help,-hβ displays a summary of command line options. your lil map of everything πΊοΈ--print-file-name,-fβ displays the name of the containing file before each string π which file did this string come from? now you know.
example:
$ llvm-strings --print-file-name test.o test.elf
test.o: _Z5hellov
test.o: some_bss
test.o: test.cpp
test.o: main
test.elf: test.cpp
test.elf: test2.cpp
test.elf: _Z5hellov
test.elf: main
test.elf: some_bss
--radix=<radix>,-tβ displays the offset within the file of each string, before the string, using the specified radix π₯. valid<radix>values areo,dandxfor octal, decimal and hexadecimal respectively, iykyk.
example:
$ llvm-strings --radix=o test.o
1054 _Z5hellov
1066 .rela.text
1101 .comment
1112 some_bss
1123 .bss
1130 test.cpp
1141 main
$ llvm-strings --radix=d test.o
556 _Z5hellov
566 .rela.text
577 .comment
586 some_bss
595 .bss
600 test.cpp
609 main
$ llvm-strings -t x test.o
22c _Z5hellov
236 .rela.text
241 .comment
24a some_bss
253 .bss
258 test.cpp
261 main
--versionβ displays the version of thellvm-stringsexecutable β@<FILE>β reads command-line options from response file<FILE>π§ cute lil options-in-a-file moment.
π EXIT STATUS π
llvm-strings exits with a non-zero exit code if there is an error π. otherwise? it exits with code 0 π slay.
π BUGS π
to report bugs, please visit https://github.com/llvm/llvm-project/labels/tools:llvm-strings/ β go off, file that issue, the maintainers wanna hear it π«Ά
π Author π
maintained by the LLVM Team (https://llvm.org/) π
π Copyright π
2003-2026, LLVM Project
and that's the whole page, bestie β this was page 23 of the LLVM-STRINGS(1) manual, dated 2026-10-20, from the LLVM source. go find some strings, ily, bye πβ¨π
π¦ where this page comes from
- arch rolling: llvm 23.1.4-1 Β· Apache-2.0 WITH LLVM-exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms