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] Add support for NetBSD/sh3 core file sections. Merge multiple copies of auxv section creation into one function.
Date: Mon, 10 Jun 2019 17:18:00 -0000	[thread overview]
Message-ID: <58e07198f34c3a8bb7d64392e8b978a0d741244e@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 58e07198f34c3a8bb7d64392e8b978a0d741244e ***

Author: Christos Zoulas <christos@zoulas.com>
Branch: master
Commit: 58e07198f34c3a8bb7d64392e8b978a0d741244e

Add support for NetBSD/sh3 core file sections.  Merge multiple copies of auxv section creation into one function.

	PR 24650
	* elf.c (elfcore_make_auxv_note_section): New function.
	(elfcore_grok_note): Use it.
	(elfcore_grok_freebsd_note): Likewise.
	(elfcore_grok_openbsd_note): Likewise.
	(elfcore_grok_netbsd_note): Likewise.  Plus add support for
	NT_NETBSDCORE_AUXV notes.


             reply	other threads:[~2019-06-10 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 17:18 sergiodj+buildbot [this message]
2019-06-10 17:19 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2019-06-10 17:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2019-06-10 17:39 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-06-10 17:45 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2019-06-10 17:49 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-06-10 17:57 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-06-10 18:04 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-06-10 18:13 ` Failures on Fedora-x86_64-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=58e07198f34c3a8bb7d64392e8b978a0d741244e@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).