objdump86(1)

📦
version 1.0.1+git20260515.8cf785f · 2 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

💖 objdump86 — the manual page, but make it cute ✨

okay bestie, pull up a chair, because we're about to get extremely cozy with three little tools that all live inside the same binary. their names are objdump86, size86, and nm86, and they're here to help you examine object, archive or executable files. yes, all three of them. no, they are not separate programs. we'll get to that. 🫶

🌸 NAME 🌸

objdump86, size86, nm86 — Examine object, archive or executable files 👑

✨ SYNOPSIS ✨

objdump86 [file...]
size86 [file...]
nm86 [file...]

no flags up in here, just vibes and file names 💅

🦋 DESCRIPTION 🦋

so like. these commands exist to let you peek inside object files. that's the whole job. iconic, honestly. and plot twist: you can also use them on archive files and executable files, because why gatekeep. when you point one of these at an archive, every module inside that archive gets processed in sequence, one after the other, like a little conga line of modules. 🎀

here's who does what:

  • nm86 — prints the symbol table in each of the files you hand it. it's giving receipts. it's giving who is this symbol and why do they think they're here.
  • size86 — displays a summary of the sizes of the segments in each of the files. short, sweet, numbers only. the strong silent type.
  • objdump86 — the main character. it decodes and displays the contents of the object files you specify. and when we say contents, we mean it: the section headers, the symbol tables, the segment sizes, and the actual segment contents. the whole meal, not just the appetizer. 🔥

💅 OPTIONS 💅

okay so here's the thing. the programs are not designed to accept any options. that's canon. that's the lore. no --help, no -v, no nothing. we respect it.

but wait — there's a whole thing you need to know. 👀

all three of objdump86, size86, and nm86 are implemented as links to the same executable file (called objdump86 in the source distribution). so the binary is one girl wearing three different outfits. which outfit she's wearing — i.e. what she actually does when you run her — is determined by the file name actually used to execute it. that's it. that's the whole mechanism. iykyk. 🧚

and if you want to force a specific behavior regardless of what file name you invoked it with, you can use one of these bad boys:

  • -s — Behave like size86. 🍓
  • -n — Behave like nm86. 🌈

periodt.

💀 RESTRICTIONS 💀

these commands are intended for use only with the Dev86/ELKS toolchain. that's it. don't bring them to other toolchains' parties. they will not slay there. they will simply not function correctly, and that's on nobody but you. 🙈

👑 SEE ALSO 👑

go read your sisters, bestie:

🌸 AUTHORS 🌸

objdump86, size86, and nm86 © 1999 Greg Haerr <greg@censoft.com>. absolute legend behavior, no cap. 💖

the manual page was written for Debian GNU/Linux, © 2006 Shyamal Prasad <shyamal@member.fsf.org>. it is distributed under the terms of the GNU General Public License version 2 (or any later version released by the Free Software Foundation). so like, share it, remix it, but keep it free, bestie. 🫶

and that's the whole page!! this masterpiece is dated May, 2006, and it comes to you straight from the source/version vibes of the objdump86(1) page itself. mwah. 😭💖

📦 where this page comes from