With 'set logging on', GDB will record its output into gdb.txt It is often desirable to include my input there as well (either so I can remember later what I was doing, or so I can take gdb.txt and attach it to a bug report directly, instead of doing screen scrape). It would also be nice to be able to timestamp output in gdb.txt, so when dealing with performance bugs, it's immediately clear which operations took how long. I think 'set logging NNN' could become a multi-state (similar to 'handle'), e.g. set logging user gdb timestamp # turn all on set logging on # alias for "set logging gdb" (backward compat) set logging off # alias for "set logging nouser nogdb notimestamp"
This overlaps with PR #8822.
I've searched for "logging" before filing this, but PR 8822 doesn't have that word in its subject. *** This bug has been marked as a duplicate of 8822 ***