From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28035 invoked by alias); 13 Mar 2012 13:46:33 -0000 Received: (qmail 28024 invoked by uid 22791); 13 Mar 2012 13:46:32 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Tue, 13 Mar 2012 13:46:13 +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 q2DDk6N9029005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Mar 2012 09:46:06 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q2DDk4xM004421; Tue, 13 Mar 2012 09:46:05 -0400 Message-ID: <4F5F4F9C.2080601@redhat.com> Date: Tue, 13 Mar 2012 13:46:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Hui Zhu CC: Hui Zhu , gdb-patches@sourceware.org, Yao Qi Subject: Re: Fix error when gdb connect to a stub that tracepoint is running[1/2] Add a flag initialized to struct trace_status References: <4F4F8BE2.7030503@mentor.com> <4F4FB2F9.80200@redhat.com> <4F4FC4AD.3020501@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2012-03/txt/msg00431.txt.bz2 On 03/11/2012 04:12 PM, Hui Zhu wrote: > Hi Pedro, > > I had made sure that the FSF acknowledged my copyright assignment mid > february. So this email is OK now. I consulted with the FSF copyright clerk, and I was told your paperwork isn't fully sort out yet, so you can't yet transfer changes on behalf of Mentor. You can however contribute your own independent changes meanwhile (under your personal assignment), as there's trust that Mentor is good about getting their paperwork in regularly. In this particular case, I've gone ahead and checked in the patches. But again, please let's make sure the paperwork is fully done before you can transfer changes on behalf of Mentor. > And I found that this issue affect 7.4 too. I suggest commit this > patch to 7.4 branch too. It'd be good to have a testcase. ;-) I'm not sure if 7.4 has all the bits necessary? I'll check it out. -- Pedro Alves