From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31936 invoked by alias); 21 Apr 2014 15:59:52 -0000 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 Received: (qmail 31927 invoked by uid 89); 21 Apr 2014 15:59:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout20.012.net.il Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 21 Apr 2014 15:59:49 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0N4E007001M5G500@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 21 Apr 2014 18:59:47 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N4E007VB1RMG700@a-mtaout20.012.net.il>; Mon, 21 Apr 2014 18:59:47 +0300 (IDT) Date: Mon, 21 Apr 2014 15:59:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] Fix "PC register is not available" issue In-reply-to: <20140421154333.GB4477@adacore.com> To: Joel Brobecker Cc: palves@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83bnvud66u.fsf@gnu.org> References: <83ioqucrkw.fsf@gnu.org> <5342DBBC.4090500@redhat.com> <83lhvh6lqi.fsf@gnu.org> <5343DE45.5050707@redhat.com> <53442710.60104@redhat.com> <83sipn6937.fsf@gnu.org> <534433A5.4060006@redhat.com> <83ob0b671j.fsf@gnu.org> <20140411200609.GM4250@adacore.com> <83d2gdhg5u.fsf@gnu.org> <20140421154333.GB4477@adacore.com> X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00405.txt.bz2 > Date: Mon, 21 Apr 2014 08:43:33 -0700 > From: Joel Brobecker > Cc: palves@redhat.com, gdb-patches@sourceware.org > > > As I wrote on gdb@, I have committed the patch to fix the GDB side of > > the problem. See below for what I actually committed, both to master > > and to the GDB 7.7 branch. > > I didn't know we were planning on putting the change in the GDB 7.7 > branch as well, but since you've tested it for several weeks, and > it's been seen by Pedro as well, we can indeed try to have it for > 7.7.1 as well. The one thing I do ask when pushing a patch to the branch > is to update the release Wiki page to add a reference to the fix: > https://sourceware.org/gdb/wiki/GDB_7.7_Release > > I've done it for you, since there was already a PR. > > > Should we now close the Bugzilla PR? If I can do that, any pointers > > as to how? > > Just log in, and change the state to "RESOLVED" + "FIXED". > I was already logged in, so did it as well. Thanks, on both accounts.