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] Use block_symbol in linespec APIs
Date: Thu, 30 Aug 2018 01:27:00 -0000 [thread overview]
Message-ID: <7e41c8db84bc6f74843dda40ae443d41977c0d20@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7e41c8db84bc6f74843dda40ae443d41977c0d20 ***
Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 7e41c8db84bc6f74843dda40ae443d41977c0d20
Use block_symbol in linespec APIs
This patch changes the linespec.c APIs to use block_symbol instead of just
a symbol. lookup_symbol et al already return block_symbol's.
gdb/ChangeLog:
* linespec.c (struct linespec) <function_symbols, label_symbols>:
Change to vector of block_symbol. Update all users.
(struct collect_info) <symbols>: Likewise.
(collect_info::add_symbol): Take block_symbol as argument.
Update all callers.
(decode_compound_collector) <m_symbols>: Change type to vector
of block_symbol. Update all users.
(decode_compound_collector::operator ()): Change parameter type
to block_symbol.
(find_method, find_function_symbols, find_linespec_symbols)
(find_label_symbols_in_block, find_label_symbols): Change symbol
vectors to block_symbol vectors.
* symtab.h (symbol_found_callback_ftype): Change parameter type to
block_symbol.
next reply other threads:[~2018-08-29 22:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 1:27 sergiodj+buildbot [this message]
2018-08-30 1:36 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2018-08-30 5:42 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-30 5:46 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-08-30 6:03 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-08-30 15:31 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-08-30 15:56 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-08-30 15:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-08-30 15:59 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-30 15:59 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-08-30 15:59 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-08-30 16:02 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-08-30 16:05 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-09-09 3:52 ` Failures on Fedora-s390x-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=7e41c8db84bc6f74843dda40ae443d41977c0d20@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).