From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105023 invoked by alias); 26 Nov 2015 07:12:40 -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 105008 invoked by uid 89); 26 Nov 2015 07:12:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mga11.intel.com Received: from mga11.intel.com (HELO mga11.intel.com) (192.55.52.93) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Nov 2015 07:12:38 +0000 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 25 Nov 2015 23:12:36 -0800 X-ExtLoop1: 1 Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by fmsmga002.fm.intel.com with ESMTP; 25 Nov 2015 23:12:36 -0800 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.138]) by IRSMSX101.ger.corp.intel.com ([169.254.1.236]) with mapi id 14.03.0248.002; Thu, 26 Nov 2015 07:12:34 +0000 From: "Metzger, Markus T" To: Pedro Alves CC: "gdb-patches@sourceware.org" Subject: RE: [PATCH] btrace: diagnose "record btrace pt" without libipt Date: Thu, 26 Nov 2015 07:12:00 -0000 Message-ID: References: <1448011026-4192-1-git-send-email-markus.t.metzger@intel.com> <564F0591.3020006@redhat.com> <564F1C3D.1040709@redhat.com> <5655E3F6.3070002@redhat.com> In-Reply-To: <5655E3F6.3070002@redhat.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00538.txt.bz2 -----Original Message----- From: Pedro Alves [mailto:palves@redhat.com]=20 Sent: Wednesday, November 25, 2015 5:38 PM To: Metzger, Markus T Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] btrace: diagnose "record btrace pt" without libipt > It would be nice if GDB could detect that record btrace is already=20 > enabled and push the record-btrace target automatically. I guess this=20 > requires some indication about the record status from gdbserver. Is=20 > there some other target that does this automatic push on (re-)connect tha= t I could use as reference? E.g., linux-thread-db.c pushes itself from a new_objfile observer (thread_d= b_new_objfile), and the spu multiarch target pushes itself from an inferio= r_created observer (spu_multiarch_inferior_created). Thanks. I'll look into those examples. It'll take a bit but I don't think= this is urgent. Are you OK to push the patch to avoid the internal error and handle the re-= connect case in a separate series? That patch might make sense for 7.10.1, as well. OK to push onto the 7.10 = branch? Regards, Markus. Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928