The documentation does not show how to save backtraces to a file. While trying to make a backtrace (something I have never done before) for avidemux I had difficulty finding out how to save to a file. gdb's internal docs, while in depth, were totally foreign to me. The documentation provided at the above url did show how to make a backtrace but not how to save it to a file. The following commands should be added to the documentation to help novices with gdb such as myself save large backtraces to files. set logging backtrace.log set logging on or just "set logging on" which will save the information to gdb.txt which can be appended to a bugreport.
Not our document; reassigning to QA.
Actually not even QA, this is just mine. And I admit I usually just copy-pasted it.
Okay I've added a couple of paragraphs and an example about this, thanks for reporting, it is indeed interesting.
