From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25687 invoked by alias); 7 Jan 2012 02:38:00 -0000 Received: (qmail 25678 invoked by uid 22791); 7 Jan 2012 02:37:58 -0000 X-SWARE-Spam-Status: No, hits=-6.7 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; Sat, 07 Jan 2012 02:37:43 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q072bh86022809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 6 Jan 2012 21:37:43 -0500 Received: from psique ([10.3.112.15]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q072bcGa019472; Fri, 6 Jan 2012 21:37:40 -0500 From: Sergio Durigan Junior To: gdb@sourceware.org Cc: Pedro Alves , Tom Tromey Subject: UST integration is broken Date: Sat, 07 Jan 2012 02:38:00 -0000 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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 X-SW-Source: 2012-01/txt/msg00026.txt.bz2 Hello, I am working on something related to static tracepoints markers, which is related to UST (http://lttng.org/ust). I did some modifications on the code, and was trying to test the result, when I realized I did not have UST installed here. Ok, so I decided to compile it and install locally just for a quick test, and after some time struggling with compilation flags, I noticed that the current UST does not support GDB anymore. For more information, see this commit: http://git.lttng.org/?p=ust.git;a=commit;h=fe566790e6be3f27f0befd85b715a3e84977bf6c I also noticed that the header file ust/ust.h is not installed, thus making the configure process useless. I am sending this message because I am in doubt about what to do: should we completely remove the support from GDB (since according to the commit message above, the implementation is going to be revamp'ed), or just temporarily disable it? I was going to send a patch for the latter, but decided to ask first. Thanks, Sergio.