public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Add file name styling to "info sharedlibrary" Date: Tue, 14 May 2019 14:08:00 -0000 [thread overview] Message-ID: <e7bd7fba34ae1f892acf1e13ac86fca55b68026d@gdb-build> (raw) *** TEST RESULTS FOR COMMIT e7bd7fba34ae1f892acf1e13ac86fca55b68026d *** Author: Tom Tromey <tromey@adacore.com> Branch: master Commit: e7bd7fba34ae1f892acf1e13ac86fca55b68026d Add file name styling to "info sharedlibrary" This changes "info sharedlibrary" to add styling to the file name. Tested on x86-64 Fedora 29. gdb/ChangeLog 2019-05-14 Tom Tromey <tromey@adacore.com> * solib.c (info_sharedlibrary_command): Style the file name. gdb/testsuite/ChangeLog 2019-05-14 Tom Tromey <tromey@adacore.com> * gdb.base/info-shared.exp (check_info_shared): Add "info shared" styling test.
next reply other threads:[~2019-05-14 14:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-14 14:08 sergiodj+buildbot [this message] 2019-05-14 14:11 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2019-05-14 14:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2019-05-14 14:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2019-05-14 14:43 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-05-14 14:45 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2019-05-14 14:55 ` Failures on Fedora-i686, " sergiodj+buildbot 2019-05-14 16:36 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2019-05-14 17:17 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2019-05-14 22:29 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+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=e7bd7fba34ae1f892acf1e13ac86fca55b68026d@gdb-build \ --to=sergiodj+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).