public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: devans@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 73be47f57c32f50d4695a4b672af9263b5313cbb Date: Fri, 08 Nov 2013 19:47:00 -0000 [thread overview] Message-ID: <20131108194747.28759.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 73be47f57c32f50d4695a4b672af9263b5313cbb (commit) from 1bd2f0baf15dfb05a884228cee1f9964768e1a27 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=73be47f57c32f50d4695a4b672af9263b5313cbb commit 73be47f57c32f50d4695a4b672af9263b5313cbb Author: Doug Evans <dje@google.com> Date: Fri Nov 8 11:47:08 2013 -0800 Change "set debug dwarf2-read" to take a verbosity level. * dwarf2read.c (dwarf2_read_debug): Change to unsigned int. (create_debug_types_hash_table): Only print debugging messages for each TU if dwarf2-read >= 2. (process_queue): Ditto. (_initialize_dwarf2_read): Make "set debug dwarf2-read" a zuinteger. Update doc string. doc/ * gdb.texinfo (Debugging Output): Update text for "set debug dwarf2-read". ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 9 +++++++++ gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 4 +++- gdb/dwarf2read.c | 30 ++++++++++++++++++++---------- 4 files changed, 37 insertions(+), 11 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2013-11-08 19:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131108194747.28759.qmail@sourceware.org \ --to=devans@sourceware.org \ --cc=src-cvs@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).