From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Jan Vrany <jan.vrany@fit.cvut.cz>, gdb-patches@sourceware.org
Subject: Regression on gdb.arch/amd64-invalid-stack-*.exp (was: Re: [RFC] mi: print frame architecture when printing frames on an MI channel)
Date: Fri, 24 Aug 2018 20:22:00 -0000 [thread overview]
Message-ID: <87zhxbplao.fsf_-_@redhat.com> (raw)
In-Reply-To: <8772378f-c4a9-fd3b-0364-bf34fdbf4a8f@redhat.com> (Pedro Alves's message of "Wed, 22 Aug 2018 12:39:25 +0100")
On Wednesday, August 22 2018, Pedro Alves wrote:
> Merged, thanks.
Hi,
This has caused a regression on the gdb.arch/amd64-invalid-stack-*.exp
tests:
Buildslave:
fedora-x86-64-4
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/10739>
Commit(s) tested:
6d52907e226ade45d5f5196eaed8386affda5156
Author(s) (in the same order as the commits):
Jan Vrany <jan.vrany@fit.cvut.cz>
Subject:
MI: Print frame architecture when printing frames on an MI channel
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-m64/6d/6d52907e226ade45d5f5196eaed8386affda5156/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.arch/amd64-invalid-stack-middle.exp: check mi -stack-list-frames command, first time
PASS -> FAIL: gdb.arch/amd64-invalid-stack-middle.exp: check mi -stack-list-frames command, second time
PASS -> FAIL: gdb.arch/amd64-invalid-stack-top.exp: check mi -stack-list-frames command, first time
PASS -> FAIL: gdb.arch/amd64-invalid-stack-top.exp: check mi -stack-list-frames command, second time
============================
Thanks to Kevin for noticing this earlier.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-08-24 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 5:57 [RFC] mi: Print frame architecture when printing frames on an MI channel Jan Vrany
2018-08-10 10:30 ` Pedro Alves
2018-08-13 10:53 ` [RFC] mi: print " Jan Vrany
2018-08-16 19:01 ` Pedro Alves
2018-08-20 10:24 ` Jan Vrany
2018-08-20 11:16 ` Pedro Alves
2018-08-20 20:43 ` Jan Vrany
2018-08-21 15:42 ` Pedro Alves
2018-08-21 16:16 ` Eli Zaretskii
2018-08-22 9:43 ` Jan Vrany
2018-08-22 11:39 ` Pedro Alves
2018-08-24 20:22 ` Sergio Durigan Junior [this message]
2018-08-27 13:37 ` Regression on gdb.arch/amd64-invalid-stack-*.exp (was: Re: [RFC] mi: print frame architecture when printing frames on an MI channel) Jan Vrany
2018-08-21 16:16 ` [RFC] mi: print frame architecture when printing frames on an MI channel Eli Zaretskii
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=87zhxbplao.fsf_-_@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--cc=palves@redhat.com \
/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).