My thought was to do a single block at the start of the script that checks for the two gdb binaries and if neither is found it exits cleanly (in particular since this runs on boot I think we want it to not whine to the console from rc.d). I think I would like a way to have it whine if run interactively, but not from rc.d whcih we could maybe do via some optional flag that rc.d/savecore always passes to it?

I was thinking the same things, but wanted to whip this out while the topic was hot. On second thought, I'll just go ahead and make those changes now.

Rework as @jhb suggested.

Harbormaster completed remote builds in B8809: Diff 27573.Apr 20 2017, 12:59 PM

vangyzen edited the test plan for this revision. (Show Details)Apr 21 2017, 1:07 PM

I've reworked the GDB removal over in D10449 which conflicts with this a bit. However, the batch mode (so messages like 'No kernel found') getting written to the core.txt.N file is still useful so it maybe that we want to refine this after D10449 goes in?

crashinfo: add "batch" mode and use it during boot

In batch mode, most messages go into the core.txt.N file
instead of stdout.

Harbormaster completed remote builds in B9533: Diff 28915.May 27 2017, 7:07 PM

vangyzen retitled this revision from crashinfo: tell the user to install GDB and suggest one way to crashinfo: add "batch" mode and use it during boot.May 27 2017, 7:08 PM

vangyzen edited the summary of this revision. (Show Details)

vangyzen edited the test plan for this revision. (Show Details)

vangyzen added inline comments.