From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb@sourceware.org
Subject: Re: 7.3->7.4 s390x regressions
Date: Thu, 22 Dec 2011 09:53:00 -0000 [thread overview]
Message-ID: <20111222095152.GA16836@host2.jankratochvil.net> (raw)
In-Reply-To: <20111218110451.GA20850@host2.jankratochvil.net>
On Sun, 18 Dec 2011 12:04:51 +0100, Jan Kratochvil wrote:
> just FYI, not sure how I get to fixing those wrt 7.4 release, I hope I will:
>
> +FAIL: gdb.base/sigstep.exp: step on breakpoint, skip handler; performing step
> +FAIL: gdb.base/sigstep.exp: return from handleri; leave handler
> +FAIL: gdb.base/sigstep.exp: return from handleri; leave signal trampoline (got interactive prompt)
> +FAIL: gdb.base/sigstep.exp: Set done as return will have skipped it
This was s390x kernel bug as reported by Ulrich:
http://www.sourceware.org/ml/gdb/2011-12/msg00039.html
> +FAIL: gdb.base/callfuncs.exp: back at main after return from call dummy breakpoint
This was a kernel difference and also got it fixed in GDB by Ulrich:
http://sourceware.org/ml/gdb-patches/2011-12/msg00652.html
Regards,
Jan
prev parent reply other threads:[~2011-12-22 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 11:05 Jan Kratochvil
2011-12-22 9:53 ` Jan Kratochvil [this message]
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=20111222095152.GA16836@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@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