BOMBARDIER(1)

πŸ“¦ version 7.44.0, in nixpkgs unstable

πŸ’₯ BOMBARDIER(1) β€” the BRL-CAD crash reporter πŸ’₯

ok so real talk, this is the bombardier page out of the BRL-CAD manual set, and yeah it's the girliest little crash reporter you've ever met πŸ’…


✨ NAME ✨

bombardier β€” the BRL-CAD graphical crash reporter 🫢


✨ SYNOPSIS ✨

bombardier [-h | -?] _logfile_...

✨ DESCRIPTION ✨

okay so bestie, listen β€” bombardier is the BRL-CAD crash reporter. literally its whole job. πŸ”₯

It reads one or more crash logfile arguments, concatenates their contents, and then pops up a Tk graphical dialog showing you all the captured crash details plus the system information. Then β€” and this is the good part β€” you can add your own description of what you were doing when it all went down, and choose to submit the report to the BRL-CAD developers at brlcad.org so they can review the stack trace. teamwork, slay πŸ’–

Also, if a logfile contains a line beginning with Command:, the token that follows gets used as the name of the application that crashed, and that's what shows up in the dialog. iconic little detail honestly πŸŽ€

If you hand it a logfile argument that doesn't exist? It gets reported as a warning and skipped. Not a whole crisis, just a warning. But heads up: at least one logfile must be supplied. no logfiles, no report, periodt πŸ’€

And the tea: bombardier is normally launched automatically by other BRL-CAD applications β€” like mged(1) β€” when they terminate unexpectedly. So you're probably not out here invoking it by hand unless you're being extra πŸ™ˆ


✨ OPTIONS ✨

  • -h β€” print a brief usage message and exit. short, sweet, done ✨
  • -? β€” print a brief usage message and exit. same vibe, different character πŸ¦‹

✨ EXAMPLES ✨

🌸 Example 1. Reviewing and submitting a crash log

bombardier ~/.brlcad/crash/mged-crash.log

This opens the crash reporter dialog populated with the contents of mged-crash.log, so the stack trace and system information can be reviewed, annotated, and submitted to the developers. lowkey the main character workflow πŸ‘‘


🌸 Example 2. Combining multiple log files into one report

bombardier mged-crash.log rt-crash.log session-env.log

This loads and concatenates several log files so that a stack trace and its related environment or session diagnostics get reviewed and submitted together as a single crash report. it's giving "bundle it up and send it" energy πŸ’…


✨ SEE ALSO ✨

brlcad(1), mged(1)


✨ AUTHOR ✨

BRL-CAD Team πŸ‘‘


This software is Copyright (c) 1989-2026 by the United States Government as represented by U.S. Army Research Laboratory.


✨ BUG REPORTS ✨

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org

like, if something's broken, tell the devs fr fr β€” that's the whole vibe πŸ’œ


okay that's the page!! from the BRL-CAD crew, this is bombardier(1) β€” go forth and submit those crash logs responsibly, bestie πŸŒˆπŸ’–

πŸ“¦ where this page comes from