From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 443 invoked by alias); 25 Nov 2013 15:14:35 -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 429 invoked by uid 89); 25 Nov 2013 15:14:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.9 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: mail-ie0-f181.google.com Received: from Unknown (HELO mail-ie0-f181.google.com) (209.85.223.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 25 Nov 2013 15:14:33 +0000 Received: by mail-ie0-f181.google.com with SMTP id e14so6829873iej.26 for ; Mon, 25 Nov 2013 07:14:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uxwsn2KVGyO/UJADouJTerpKUFFRACSkeqYmjD2pCiI=; b=g7lyEV5O1FxygFhRC3zH9KWKoJq7mv9yco26pfyqi4SyhQL1ej1yIY13xq/bdKLvHM sALLlHgb0IBL3MQmk2aizzSNnwcyTOkDZNad/mEaDoqCe3XpFu0/nRxAae9wCVuuXSUo lcf4dX0jUtQfgdn5FL/npj1pplp2fqs3JTrcie/biBqchb+IRqm17zYrkXEQq+HU2Fhy YZcBEIbRnv1la8yjkAUTQd4pJRSMVT+cYWT4d5+vhhpQD1ujmIfsHbr/zxvO+ue/upvD F1RdZHB8OkFHRzZ4CZ203XYG2BWCpGyy9Lb8CYF/zGjiKemTzBPNBhBCxaanLM57qpU7 +f/w== X-Gm-Message-State: ALoCoQmD0e1XqklCigfpRQ0fCJZYit3Qlzh0PIlegbK0dUcv59hItfNDlnmt3Dz4oUWeOwngI5d/ MIME-Version: 1.0 X-Received: by 10.42.110.147 with SMTP id q19mr16422754icp.6.1385392465439; Mon, 25 Nov 2013 07:14:25 -0800 (PST) Received: by 10.64.20.52 with HTTP; Mon, 25 Nov 2013 07:14:25 -0800 (PST) In-Reply-To: <20131125130250.GE3114@adacore.com> References: <20131125125128.GA3153@adacore.com> <20131125130250.GE3114@adacore.com> Date: Mon, 25 Nov 2013 15:24:00 -0000 Message-ID: Subject: Re: gdbserver, aarch64: Zero out regs in aarch64_linux_set_debug_regs From: Will Newton To: Joel Brobecker Cc: "gdb-patches@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00780.txt.bz2 On 25 November 2013 13:02, Joel Brobecker wrote: >> > We're about to create a 7.6.2 release. To help me sent release >> > announcements, I need an entry in the wiki page we created for >> > that release branch. For 7.6.2, that's: >> > >> > https://sourceware.org/gdb/wiki/GDB_7.6_Release >> > >> > Can you please add an entry that follows the format used in >> > the entries added for the 7.6.1 release? >> >> Sure, no problem. > > Thanks! > >> > I tried doing that myself, but got lost a little. AFAICT, you're >> > applying the same patch as one that was applied on the GDB side. >> > I traced the problem description back to a patch first posted in >> > July, but: 1. Does your patch fix the same problem/symptoms? >> >> It fixes the same issue in gdbserver that was fixed in gdb. >> >> > 2. The gdb-side patch in not part of the gdb_7_6-branch; >> > is that what we want? >> >> Not really! I believed that the gdb patch had been committed to the >> stable branch but later discovered that it hadn't. As the stable >> branch appeared to be dormant I didn't follow up on it. Ideally both >> patches should be applied and if we are going to do another release >> I'm happy to cherry pick it across. > > Let's do that, then. I think it'll make better sense for the user, > and it'll also be easier to describe the extent of the problem being > fixed. Just to confirm - this patch should be applied to the gdb_7_6-branch in CVS? -- Will Newton Toolchain Working Group, Linaro