From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22706 invoked by alias); 21 Dec 2011 19:41:27 -0000 Received: (qmail 22695 invoked by uid 22791); 21 Dec 2011 19:41:25 -0000 X-SWARE-Spam-Status: No, hits=-7.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Dec 2011 19:40:59 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBLJevtH011290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2011 14:40:57 -0500 Received: from host2.jankratochvil.net (ovpn-116-60.ams2.redhat.com [10.36.116.60]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pBLJerMC002988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 21 Dec 2011 14:40:56 -0500 Date: Wed, 21 Dec 2011 20:47:00 -0000 From: Jan Kratochvil To: Ulrich Weigand Cc: gdb-patches@sourceware.org Subject: Re: [commit, s390] Fix regression in gdb.base/callfuncs.exp [Re: [commit, s390] Proper handling of PSW address/mask everywhere] Message-ID: <20111221194053.GA30628@host2.jankratochvil.net> References: <20111219225612.GA29085@host2.jankratochvil.net> <201112211937.pBLJbGUQ019925@d06av02.portsmouth.uk.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201112211937.pBLJbGUQ019925@d06av02.portsmouth.uk.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00744.txt.bz2 On Wed, 21 Dec 2011 20:37:16 +0100, Ulrich Weigand wrote: > Jan Kratochvil wrote: > > There are yet some regressions of sigstep.exp, I will check them more: > > Hmm, I'm not seeing this particular symptom you mention below. I looked at it and I have seen it broken enough already in 7.3, due to some kernel bug. Nice to know it is therefore fixed in kernel GIT now. This whole sigstep.exp issue is therefore a kernel one and not GDB one. Thanks, Jan