From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30186 invoked by alias); 21 Jan 2010 16:52:23 -0000 Received: (qmail 30171 invoked by uid 48); 21 Jan 2010 16:52:22 -0000 Date: Thu, 21 Jan 2010 16:52:00 -0000 From: "ppluzhnikov at google dot com" To: gdb-prs@sourceware.org Message-ID: <20100121165222.11204.ppluzhnikov@google.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug cli/11204] New: Make logging more flexible X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00070.txt.bz2 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.