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] Allow hiding of some filtered frames
Date: Tue, 27 Mar 2018 04:49:00 -0000 [thread overview]
Message-ID: <978d6c756fcb0332ddf12e19305dd0e53b98a93d@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 978d6c756fcb0332ddf12e19305dd0e53b98a93d ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 978d6c756fcb0332ddf12e19305dd0e53b98a93d
Allow hiding of some filtered frames
When a frame filter elides some frames, they are still printed by
"bt", indented a few spaces. PR backtrace/15582 notes that it would
be nice for users if elided frames could simply be dropped. This
patch adds this capability.
gdb/ChangeLog
2018-03-26 Tom Tromey <tom@tromey.com>
PR backtrace/15582:
* stack.c (backtrace_command): Parse "hide" argument.
* python/py-framefilter.c (py_print_frame): Handle PRINT_HIDE.
* extension.h (enum frame_filter_flags) <PRINT_HIDE>: New
constant.
gdb/doc/ChangeLog
2018-03-26 Tom Tromey <tom@tromey.com>
PR backtrace/15582:
* gdb.texinfo (Backtrace): Mention "hide" argument.
gdb/testsuite/ChangeLog
2018-03-26 Tom Tromey <tom@tromey.com>
PR backtrace/15582:
* gdb.python/py-framefilter.exp: Add "bt hide" test.
next reply other threads:[~2018-03-27 4:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 4:49 sergiodj+buildbot [this message]
2018-03-27 4:49 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-27 5:17 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-27 6:06 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-27 6:35 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-03-27 7:13 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-27 7:40 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-27 8:07 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-03-27 8:09 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-27 8:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-03-27 8:32 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-27 8:39 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-03-27 8:47 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2018-03-27 9:10 ` Failures on Fedora-x86_64-cc-with-index, " 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=978d6c756fcb0332ddf12e19305dd0e53b98a93d@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: 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).