public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/11204] New: Make logging more flexible Date: Thu, 21 Jan 2010 16:52:00 -0000 [thread overview] Message-ID: <20100121165222.11204.ppluzhnikov@google.com> (raw) 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" -- Summary: Make logging more flexible Product: gdb Version: 7.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: cli AssignedTo: ppluzhnikov at google dot com ReportedBy: ppluzhnikov at google dot com CC: gdb-prs at sourceware dot org GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=11204 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-01-21 16:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-21 16:52 ppluzhnikov at google dot com [this message] 2010-01-21 16:54 ` [Bug cli/11204] " ppluzhnikov at google dot com 2010-01-22 16:55 ` tromey at redhat dot com 2010-01-22 17:00 ` ppluzhnikov at google dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100121165222.11204.ppluzhnikov@google.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).