FERROR(1)

πŸ“¦ version 0.4, in fedora 43, fedora 44

πŸ’– FERROR(1) β€” the Frysk girlies' stack-trace detector πŸ’–

okay bestie, sit down, hydrate, because this one is so cool. this is ferror, part of the Frysk family, and it's basically a little snitch that watches your program and screams (politely, with a stack trace) the second it prints a message you care about. 🫢


✨ NAME ✨

ferror β€” print a stack trace when the given message is printed by the traced program πŸ’…


🌸 SYNOPSIS 🌸

ferror [options] {program arg ...  | pid...}

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜•: ferror monitors the processes write system call for the specified MESSAGE, and when it catches it, it prints a stack trace of the process at the point of the write. like, exactly where it happened. no cap. it's giving surveillance but make it helpful. πŸ‘‘

πŸŽ€ Stack Print Options πŸŽ€

these control how much detail you get in your lil' backtrace. pick your vibe:

  • -number-of-frames count β€” limits the back-trace to count frames. the default is to limit the back-trace to 10 frames. specify 0 or "all" if you want every single frame, no holding back. πŸ”₯
  • -lite β€” does a light-weight stack backtrace with only minimal information. literally equivalent to -print -. lowkey minimal, highkey useful. ✨
  • -rich β€” does a detailed stack back-trace that includes, where possible, inlined function calls, parameter names and values, and debug-names. equivalent to -print inline,params,debug-names. this one ATE. πŸ’…
  • -print print-option,... β€” tells ferror what level of detail to include in a stack back-trace. print-option can be any of these cuties:
    • debug-names: use debug information, such as DWARF, to determine the name of functions 🧚
    • paths: include the full path to source files and libraries 🌈
    • inline: include in-line function in back-trace ⭐
    • locals: to include local variables from each frame πŸ“
    • params: include the function parameters πŸ’œ
to negate a print-option, prefix it with -. (yes, a little minus sign. iconic behaviour. πŸ™ˆ)

πŸ‘‘ Standard Frysk Options πŸ‘‘

the family classics, every Frysk tool gets these:

  • -exe β€” the full path of the executable to read. πŸ“‚
  • -noexe β€” do not attempt to read the corresponding executable when loading a core file. πŸ™…β™€οΈ
  • -sysroot directory β€” the system root directory under which all executables, libraries, and source are located. 🌳
  • -debug class=level... β€” sets internal debug-tracing of the specified Java class to level. level can be NONE, INFO, WARNING, FINE, and FINEST. if the level is absent, FINE is assumed; if the class is absent, the global level is set. πŸ›

πŸ’€ EXAMPLE πŸ’€

like, run this and watch the magic:

ferror -e "No such file or directory" -- ls fake

🌟 SEE ALSO 🌟

  • frysk(7) β€” go read the whole family lore, bestie πŸ“–

😭 BUGS 😭

found something cursed? report bugs to http://sourceware.org/frysk β€” they wanna hear it fr fr. 🫢


and that's the whole page, gorgeous. this one's from Frysk 0.4-99.fc43, dated April 2008 β€” yes she's vintage, yes she still slays, we stan a legacy icon. πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from
  • fedora 43: frysk 0.4-99.fc43 Β· GPL-2.0-only WITH 389-exception AND GPL-2.0-or-later WITH Classpath-exception-2.0 AND MIT
  • fedora 44: frysk 0.4-99.fc43 Β· GPL-2.0-only WITH 389-exception AND GPL-2.0-or-later WITH Classpath-exception-2.0 AND MIT
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms