From: Markus Metzger <markus.t.metzger@intel.com>
To: palves@redhat.com
Cc: gdb-patches@sourceware.org
Subject: [PATCH v3 10/15] btrace: less debug output
Date: Thu, 29 Jan 2015 17:11:00 -0000 [thread overview]
Message-ID: <1422548899-9789-11-git-send-email-markus.t.metzger@intel.com> (raw)
In-Reply-To: <1422548899-9789-1-git-send-email-markus.t.metzger@intel.com>
For some programs, "set debug record 1" will print tons of "no lines at
0x..." messages. This is not always helpful.
Change it to only print those messages for values bigger than 1.
2015-01-29 Markus Metzger <markus.t.metzger@intel.com>
gdb/
* btrace.c (ftrace_update_lines): Add record_debug check.
---
gdb/btrace.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/btrace.c b/gdb/btrace.c
index 206e692..b29e0b2 100644
--- a/gdb/btrace.c
+++ b/gdb/btrace.c
@@ -554,7 +554,8 @@ ftrace_update_lines (struct btrace_function *bfun, CORE_ADDR pc)
sal = find_pc_line (pc, 0);
if (sal.symtab == NULL || sal.line == 0)
{
- DEBUG_FTRACE ("no lines at %s", core_addr_to_string_nz (pc));
+ if (record_debug > 1)
+ DEBUG_FTRACE ("no lines at %s", core_addr_to_string_nz (pc));
return;
}
--
1.8.3.1
next prev parent reply other threads:[~2015-01-29 16:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:28 [PATCH v3 00/15] record btrace: prepare for a new trace format Markus Metzger
2015-01-29 16:29 ` [PATCH v3 13/15] btrace: increase buffer size for exception test Markus Metzger
2015-01-29 16:29 ` [PATCH v3 02/15] btrace: add format argument to supports_btrace Markus Metzger
2015-01-29 16:29 ` [PATCH v3 08/15] btrace: identify cpu Markus Metzger
2015-01-29 16:29 ` [PATCH v3 12/15] btrace: support 32-bit inferior on 64-bit host Markus Metzger
2015-01-29 16:29 ` [PATCH v3 07/15] btrace: extend struct btrace_insn Markus Metzger
2015-01-29 16:29 ` [PATCH v3 05/15] record-btrace: add bts buffer size configuration option Markus Metzger
2015-01-29 16:30 ` [PATCH v3 09/15] record-btrace: indicate gaps Markus Metzger
2015-01-29 16:30 ` [PATCH v3 01/15] btrace: add struct btrace_data Markus Metzger
2015-01-29 16:30 ` [PATCH v3 06/15] btrace: update btrace_compute_ftrace parameters Markus Metzger
2015-01-29 16:30 ` [PATCH v3 14/15] configure: check for libipt Markus Metzger
2015-01-29 16:33 ` [PATCH v3 11/15] btrace: work around _dl_runtime_resolve returning to resolved function Markus Metzger
2015-01-29 17:11 ` [PATCH v3 03/15] btrace, linux: add perf event buffer abstraction Markus Metzger
2015-01-29 17:11 ` Markus Metzger [this message]
2015-01-29 18:35 ` [PATCH v3 04/15] record btrace: add configuration struct Markus Metzger
2015-01-29 19:29 ` Eli Zaretskii
2015-01-29 19:28 ` [PATCH v3 15/15] [wip] btrace: support Intel(R) Processor Trace Markus Metzger
2015-01-29 19:28 ` Eli Zaretskii
2015-01-30 18:57 ` Metzger, Markus T
2015-02-04 8:25 ` [PATCH v3 00/15] record btrace: prepare for a new trace format Metzger, Markus T
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=1422548899-9789-11-git-send-email-markus.t.metzger@intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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).