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 some cleanups from record-full.c Date: Fri, 23 Mar 2018 03:37:00 -0000 [thread overview] Message-ID: <a2b2bc12af45f48617729c1413a1a01c0ee957ca@gdb-build> (raw) *** TEST RESULTS FOR COMMIT a2b2bc12af45f48617729c1413a1a01c0ee957ca *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: a2b2bc12af45f48617729c1413a1a01c0ee957ca Remove some cleanups from record-full.c This removes some cleanups from record-full.c in a straightforward way. Tested by the buildbot. gdb/ChangeLog 2018-03-22 Tom Tromey <tom@tromey.com> * record-full.c (record_full_exec_insn): Use gdb::byte_vector. (record_full_goto_bookmark): Use std::string.
next reply other threads:[~2018-03-23 3:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-23 3:37 sergiodj+buildbot [this message] 2018-03-23 3:37 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot 2018-03-23 3:42 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-23 3:44 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-03-23 3:45 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-23 3:53 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-23 3:54 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-23 4:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-23 4:07 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-23 4:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2018-03-23 4:20 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-23 4:22 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-03-23 4:46 ` Failures on Ubuntu-AArch32-m32, " 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=a2b2bc12af45f48617729c1413a1a01c0ee957ca@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).