public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Remove two TUI comments Date: Wed, 16 Oct 2019 02:58:00 -0000 [thread overview] Message-ID: <d2dd1084c10839efb916a0bfe57ca7a056d08b47@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d2dd1084c10839efb916a0bfe57ca7a056d08b47 *** commit d2dd1084c10839efb916a0bfe57ca7a056d08b47 Author: Tom Tromey <tom@tromey.com> AuthorDate: Tue Oct 1 16:58:26 2019 -0600 Commit: Tom Tromey <tom@tromey.com> CommitDate: Wed Oct 9 16:50:33 2019 -0600 Remove two TUI comments This removes two comments from tui.h. These were not useful. gdb/ChangeLog 2019-10-09 Tom Tromey <tom@tromey.com> * tui/tui.h: Remove comments. diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 9402ba4111..f6c800da77 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2019-10-09 Tom Tromey <tom@tromey.com> + + * tui/tui.h: Remove comments. + 2019-10-09 Tom de Vries <tdevries@suse.de> * python/lib/gdb/printer/bound_registers.py: Use diff --git a/gdb/tui/tui.h b/gdb/tui/tui.h index baf4a813b6..dac410fcfa 100644 --- a/gdb/tui/tui.h +++ b/gdb/tui/tui.h @@ -45,8 +45,6 @@ enum tui_win_type DATA_ITEM_WIN }; -/* GENERAL TUI FUNCTIONS */ -/* tui.c */ extern CORE_ADDR tui_get_low_disassembly_address (struct gdbarch *, CORE_ADDR, CORE_ADDR); extern void tui_show_assembly (struct gdbarch *gdbarch, CORE_ADDR addr);
next reply other threads:[~2019-10-16 2:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-16 2:58 gdb-buildbot [this message] 2019-10-16 2:58 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2019-10-16 5:18 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2019-10-22 11:35 ` Failures on Fedora-i686, " gdb-buildbot 2019-10-22 12:26 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2019-10-22 12:28 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-10-22 13:12 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-10-22 13:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-10-22 14:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2019-10-22 14:55 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
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=d2dd1084c10839efb916a0bfe57ca7a056d08b47@gdb-build \ --to=gdb-buildbot@sergiodj.net \ --cc=gdb-testers@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).