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] Remove cleanups from check_fast_tracepoint_sals
Date: Sat, 24 Feb 2018 17:19:00 -0000	[thread overview]
Message-ID: <281d762b1a56317171e462666b98d50bfa31a08a@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 281d762b1a56317171e462666b98d50bfa31a08a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 281d762b1a56317171e462666b98d50bfa31a08a

Remove cleanups from check_fast_tracepoint_sals

This changes the gdbarch fast_tracepoint_valid_at method to use a
std::string as its out parameter, and then updates all the uses.  This
allows removing a cleanup from breakpoint.c.

Regression tested by the buildbot.

ChangeLog
2018-02-24  Tom Tromey  <tom@tromey.com>

	* i386-tdep.c (i386_fast_tracepoint_valid_at): "msg" now a
	std::string.
	* gdbarch.sh (fast_tracepoint_valid_at): Change "msg" to a
	std::string*.
	* gdbarch.c: Rebuild.
	* gdbarch.h: Rebuild.
	* breakpoint.c (check_fast_tracepoint_sals): Use std::string.
	* arch-utils.h (default_fast_tracepoint_valid_at): Update.
	* arch-utils.c (default_fast_tracepoint_valid_at): "msg" now a
	std::string*.


             reply	other threads:[~2018-02-24 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 17:19 sergiodj+buildbot [this message]
2018-02-24 17:19 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-24 17:21 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-24 17:26 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-24 17:27 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-24 17:37 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-24 17:42 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-24 17:43 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-24 17:44 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-24 18:01 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-24 18:55 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-02-25 20:10 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-26 17:19 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-02-26 17:34 ` 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=281d762b1a56317171e462666b98d50bfa31a08a@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).