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/8822] log commands along with their output (make logging
Date: Fri, 22 Jan 2010 17:06:00 -0000 [thread overview]
Message-ID: <20100122170603.28693.qmail@sourceware.org> (raw)
In-Reply-To: <20040722184800.8822.lee@bustech.com>
------- Additional Comments From ppluzhnikov at google dot com 2010-01-22 17:06 -------
>From PR 11204:
---
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"
---
The advantage of GDB logging over script(1) is that it eliminates "line noise"
-- all the ^R and ^H that make script log hard to read and understand.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at sourceware dot|ppluzhnikov at google dot
|org |com
Summary|log commands along with |log commands along with
|their output |their output (make logging
http://sourceware.org/bugzilla/show_bug.cgi?id=8822
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-01-22 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040722184800.8822.lee@bustech.com>
2010-01-22 17:00 ` [Bug cli/8822] log commands along with their output ppluzhnikov at google dot com
2010-01-22 17:06 ` ppluzhnikov at google dot com [this message]
2010-01-22 17:07 ` [Bug cli/8822] log commands along with their output (make logging more flexible) 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=20100122170603.28693.qmail@sourceware.org \
--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: link
Be 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).