FERROR(1)
π 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 tocountframes. the default is to limit the back-trace to 10 frames. specify0or"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,...β tellsferrorwhat level of detail to include in a stack back-trace.print-optioncan 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 tolevel.levelcan beNONE,INFO,WARNING,FINE, andFINEST. if the level is absent,FINEis 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