public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Regressions on s390x RHEL-6.5 (was: Re: GDB 7.6.90 available for testing)
Date: Thu, 09 Jan 2014 18:27:00 -0000	[thread overview]
Message-ID: <m38uupovst.fsf@redhat.com> (raw)
In-Reply-To: <20140108101428.C2280E003F@joel.gnat.com> (Joel Brobecker's	message of "Wed, 8 Jan 2014 14:14:28 +0400 (RET)")

On Wednesday, January 08 2014, Joel Brobecker wrote:

> A gzip'ed version is also available: gdb-7.6.90.tar.gz.
>
> Please give it a test if you can and report any problems you might find.

Thank you very much for all the effort you put in the release process,
Joel.  I second what Tom already said in another message :-).

Having said that, I am now testing the 7.7 against some architectures of
interest.  I will send e-mails separately for different arch's, to
organize things better.  These are the regressions I found (and have not
investigated yet) on s390x with RHEL-6.5.

  -PASS: gdb.server/server-kill.exp: tstatus
  +FAIL: gdb.server/server-kill.exp: tstatus

  -PASS: gdb.trace/mi-traceframe-changed.exp: tfile: -trace-find frame-number 0
  +FAIL: gdb.trace/mi-traceframe-changed.exp: tfile: -trace-find frame-number 0

There are also some newly introduced failures:

  +FAIL: gdb.dwarf2/dwz.exp: p the_int

  +FAIL: gdb.dwarf2/implptrpiece.exp: print/d p[-1]

  +FAIL: gdb.server/wrapper.exp: continue to marker
  +FAIL: gdb.server/wrapper.exp: print d

  +FAIL: gdb.trace/entry-values.exp: disassemble foo+52,+10

As I said, I still haven't investigated them, but I plan to do so soon
enough (for now I'm still running tests on other arch's).

Thanks,

-- 
Sergio

  parent reply	other threads:[~2014-01-09 18:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 10:14 GDB 7.6.90 available for testing Joel Brobecker
2014-01-08 18:18 ` Reini Urban
2014-01-09  2:46   ` Joel Brobecker
2014-01-09 17:07   ` Tom Tromey
2014-01-10  4:25     ` Joel Brobecker
2014-01-10  1:52   ` Yao Qi
2014-01-09 18:27 ` Sergio Durigan Junior [this message]
2014-01-11  8:56 ` Eli Zaretskii
2014-01-13 17:33   ` Eli Zaretskii
2014-01-13 17:51   ` Pedro Alves
2014-01-13 18:28     ` Eli Zaretskii
2014-01-13 18:44       ` Pedro Alves
2014-01-13 18:50         ` Eli Zaretskii
2014-01-13 19:15           ` Eli Zaretskii
2014-01-13 19:53             ` Pedro Alves
2014-01-13 20:33               ` Eli Zaretskii
2014-01-15 16:33               ` Eli Zaretskii
2014-01-13 10:29 ` Ricard Wanderlof
2014-01-13 10:37   ` Joel Brobecker

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=m38uupovst.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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).