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 mdebugread.c
Date: Fri, 11 May 2018 17:54:00 -0000	[thread overview]
Message-ID: <633cf2548bcd3dafe297e21a1dd3574240280d48@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 633cf2548bcd3dafe297e21a1dd3574240280d48 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 633cf2548bcd3dafe297e21a1dd3574240280d48

Remove cleanups from mdebugread.c

This removes the remaining cleanups from mdebugread.c, replacing them
with gdb::def_vector.

Tested by the buildbot, though I doubt this exercises mdebugread.

gdb/ChangeLog
2018-05-11  Tom Tromey  <tom@tromey.com>

	* mdebugread.c (parse_partial_symbols, psymtab_to_symtab_1): Use
	gdb::def_vector.


             reply	other threads:[~2018-05-11 17:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 17:54 sergiodj+buildbot [this message]
2018-05-11 18:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-11 19:10 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-05-12 20:26 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-05-12 21:45 ` *** COMPILATION FAILED *** Failures on Fedora-i686, branch master *** BREAKAGE *** sergiodj+buildbot
2018-05-12 21:55 ` Failures on Fedora-x86_64-cc-with-index, branch master sergiodj+buildbot
2018-05-12 22:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-05-13  0:56 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-06-21  3:28 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2018-06-21  8:59 ` 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=633cf2548bcd3dafe297e21a1dd3574240280d48@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).