From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32221 invoked by alias); 1 Mar 2013 07:55:58 -0000 Received: (qmail 32209 invoked by uid 22791); 1 Mar 2013 07:55:56 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Mar 2013 07:55:51 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1UBKoo-0005R0-BD from Yao_Qi@mentor.com ; Thu, 28 Feb 2013 23:55:50 -0800 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Feb 2013 23:55:50 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.1.289.1; Thu, 28 Feb 2013 23:55:49 -0800 Message-ID: <51305ED5.7000706@codesourcery.com> Date: Fri, 01 Mar 2013 07:55:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Pedro Alves CC: Subject: Re: [PATCH 3/5] Read CTF by the ctf target References: <1361931459-3953-1-git-send-email-yao@codesourcery.com> <1361931459-3953-4-git-send-email-yao@codesourcery.com> <512F9182.3080104@redhat.com> In-Reply-To: <512F9182.3080104@redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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: 2013-03/txt/msg00002.txt.bz2 On 03/01/2013 01:18 AM, Pedro Alves wrote: > We know from previous patches that the latest released > babeltrace breaks gdb, due to the lookup_enum function. Does > this catch that? I see namespacing fixes going into > babeltrace as recently as last 15th. Do we know if We are using babeltrace trunk now, so the problem of lookup_enum function goes away. > babeltrace's API is more or less done and close to a release? > I am not sure, but looks the babeltrace's APIs are quite stable. I don't see the schedule of the next babeltrace release on its website. However, since we start to use babeltrace in GDB, I'll keep my eyes on it and run GDB testsuite along with babeltrace trunk to make sure nothing is broken. >> >+ ],[], >> >+ [AC_MSG_RESULT([yes]); AC_DEFINE(HAVE_LIBBABELTRACE, 1, [Define if libbabeltrace is available])], >> >+ [AC_MSG_RESULT([no]); btlibs= ; btinc= ]) >> >+ CFLAGS="$saved_CFLAGS" >> >+fi >> >+ >> >+# Flags needed for UST > babeltrace > A copy-paste error. I'll post a updated patched soon. -- Yao (齐尧)