From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54869 invoked by alias); 17 May 2016 16:27:19 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 54844 invoked by uid 89); 17 May 2016 16:27:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=HTo:U*me, huey, Huey X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 17 May 2016 16:27:08 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CF0AC85543; Tue, 17 May 2016 16:27:06 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u4HGR5DD015335; Tue, 17 May 2016 12:27:05 -0400 Subject: Re: [regression] gdb 7.11 breaks rr To: Kyle Huey , gdb@sourceware.org References: Cc: rr-dev From: Pedro Alves Message-ID: <4ec4cc6e-3bfd-6974-3a82-64c36799eb30@redhat.com> Date: Tue, 17 May 2016 16:27:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-05/txt/msg00007.txt.bz2 On 05/16/2016 11:06 PM, Kyle Huey wrote: > This was fixed after the release of gdb 7.11 by [1]. I verified that > cherry-picking this commit on top of the gdb-7.11-release tag also fixes > rr. Could we get this commit backported for a 7.11.1? It actually was already, at the time: https://sourceware.org/ml/gdb-patches/2016-04/msg00277.html Git commit 6b9ef0d488c556339aea7b095ef7a9b6bf6b1af1. Try the gdb-7.11-branch branch (where 7.11.1 will be released from), instead of the 7.11 release tag, which is frozen. Thanks, Pedro Alves