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] alpha-bsd-nat: Use ptid from regcache instead of inferior_ptid
Date: Wed, 22 Mar 2017 12:42:00 -0000 [thread overview]
Message-ID: <f79ec2066662b2c32c9e62ee372c9c230d206b89@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT f79ec2066662b2c32c9e62ee372c9c230d206b89 ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f79ec2066662b2c32c9e62ee372c9c230d206b89
alpha-bsd-nat: Use ptid from regcache instead of inferior_ptid
gdb/ChangeLog:
* alpha-bsd-nat.c (alphabsd_fetch_inferior_registers,
alphabsd_store_inferior_registers): Use regcache->ptid instead
of inferior_ptid.
next reply other threads:[~2017-03-22 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:42 sergiodj+buildbot [this message]
2017-03-22 12:42 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, branch master sergiodj+buildbot
2017-03-22 13:09 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-03-22 17:36 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-03-22 17:58 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-03-22 18:19 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-04-03 3:32 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-04-03 12:39 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2017-04-03 19:40 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2017-04-04 4:51 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-04-04 14:03 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-04-09 18:02 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-04-10 4:21 ` Failures on Fedora-ppc64le-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=f79ec2066662b2c32c9e62ee372c9c230d206b89@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).