STRINGS(1)

✨ STRINGS(1) ✨

okay bestie, welcome to strings from the GNU Development Tools fam 💖 this is the manual page, but make it make sense.

---

🌸 NAME 🌸

strings — print the sequences of printable characters in files

---

🎀 SYNOPSIS 🎀

strings [-afovV] [-min-len]
        [-n min-len] [--bytes=min-len]
        [-t radix] [--radix=radix]
        [-e encoding] [--encoding=encoding]
        [-] [--all] [--print-file-name]
        [-T bfdname] [--target=bfdname]
        [-w] [--include-all-whitespace]
        [-s] [--output-separatorsep_string]
        [--help] [--version] file...

---

🦋 DESCRIPTION 🦋

so for every file you hand over, GNU strings prints out the printable character sequences that are at least 4 characters long (or however long you told it with the options below), and that are followed by an unprintable character. it's giving "find the words hiding in the binary" 💅

depending on how the strings program was configured, it'll default to either:

• showing all the printable sequences it can find in each file, or
• showing only the sequences that live in loadable, initialized data sections.

if the file type is unrecognizable, or if strings is reading from stdin, then bestie it will always display all of the printable sequences that it can find. no gatekeeping. periodt.

for backwards compatibility, any file that shows up after a command-line option of just - will also be scanned in full, regardless of whether a -d option is hanging around. lowkey iconic of it honestly.

strings is mainly useful for determining the contents of non-text files. fr fr that's the whole vibe.

---

💅 OPTIONS 💅

• -a, --all — scan the whole file, regardless of what sections it contains or whether those sections are loaded or initialized. normally this is the default behaviour, but strings can be configured so that the -d is the default instead. the - option is position dependent and forces strings to perform full scans of any file that is mentioned after the - on the command line, even if the -d option has been specified. yes ma'am, order matters 😤
• -d, --data — only print strings from initialized, loaded data sections in the file. this may reduce the amount of garbage in the output, but it also exposes the strings program to any security flaws that may be present in the BFD library used to scan and load sections. strings can be configured so that this option is the default behaviour. in such cases the -a option can be used to avoid using the BFD library and instead just print all of the strings found in the file.

ngl bestie, that security note is not a vibe. read it twice. 👀

• -f, --print-file-name — print the name of the file before each string. very "who said that" of it 🎤
• --help — print a summary of the program usage on the standard output and exit. your little cheat sheet 🫶
• -min-len, -n min-len, --bytes=min-len — print sequences of characters that are at least min-len characters long, instead of the default 4.
• -o — like -t o. some other versions of strings have -o act like -t d instead. since we can not be compatible with both ways, we simply chose one. we picked one and we're standing by it, no take-backs 💀
• -t radix, --radix=radix — print the offset within the file before each string. the single character argument specifies the radix of the offset---o for octal, x for hexadecimal, or d for decimal.
• -e encoding, --encoding=encoding — select the character encoding of the strings that are to be found. possible values for encoding are: s = single-7-bit-byte characters (ASCII, ISO 8859, etc., default), S = single-8-bit-byte characters, b = 16-bit bigendian, l = 16-bit littleendian, B = 32-bit bigendian, L = 32-bit littleendian. useful for finding wide character strings. (l and b apply to, for example, Unicode UTF-16/UCS-2 encodings).
• -T bfdname, --target=bfdname — specify an object code format other than your system's default format.
• -v, -V, --version — print the program version number on the standard output and exit. number check ✨
• -w, --include-all-whitespace — by default tab and space characters are included in the strings that are displayed, but other whitespace characters, such a newlines and carriage returns, are not. the -w option changes this so that all whitespace characters are considered to be part of a string.
• -s, --output-separator — by default, output strings are delimited by a new-line. this option allows you to supply any string to be used as the output record separator. useful with --include-all-whitespace where strings may contain new-lines internally.
• @file — read command-line options from file. the options read are inserted in place of the original @file option. if file does not exist, or cannot be read, then the option will be treated literally, and not removed.

options in file are separated by whitespace. a whitespace character may be included in an option by surrounding the entire option in either single or double quotes. any character (including a backslash) may be included by prefixing the character to be included with a backslash. the file may itself contain additional @file options; any such options will be processed recursively.

recursive @file?? it's giving inception 🌀 it works, just don't get lost in there.

---

🌈 SEE ALSO 🌈

ar(1), nm(1), objdump(1), ranlib(1), readelf(1) and the Info entries for binutils.

---

👑 COPYRIGHT 👑

Copyright (c) 1991-2020 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

---

and that's the whole page bestie 💜 this one's from binutils-2.35.1, dated 2022-11-21, and it ate. go read some binaries, you've got this 🌸🦋