From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <binutils-return-105602-listarch-binutils=sources.redhat.com@sourceware.org>
Received: (qmail 57920 invoked by alias); 8 May 2019 14:34:07 -0000
Mailing-List: contact binutils-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <binutils.sourceware.org>
List-Subscribe: <mailto:binutils-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/binutils/>
List-Post: <mailto:binutils@sourceware.org>
List-Help: <mailto:binutils-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: binutils-owner@sourceware.org
Received: (qmail 57912 invoked by uid 89); 8 May 2019 14:34:07 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=shipped, actively, company, our
X-HELO: mx1.suse.de
Received: from mx2.suse.de (HELO mx1.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 May 2019 14:34:06 +0000
Received: from relay2.suse.de (unknown [195.135.220.254])	by mx1.suse.de (Postfix) with ESMTP id 1FABBAD05;	Wed,  8 May 2019 14:34:03 +0000 (UTC)
Date: Wed, 08 May 2019 14:34:00 -0000
From: Michael Matz <matz@suse.de>
To: Nick Clifton <nickc@redhat.com>
cc: Nick Alcock <nick.alcock@oracle.com>,     Joseph Myers <joseph@codesourcery.com>, binutils@sourceware.org
Subject: Re: [PATCH 00/19] libctf, and CTF support for objdump and readelf
In-Reply-To: <534c2613-da1e-7b53-338c-2988b44b1b6b@redhat.com>
Message-ID: <alpine.LSU.2.21.1905081428580.8064@wotan.suse.de>
References: <20190430225706.159422-1-nick.alcock@oracle.com> <alpine.DEB.2.21.1905021508230.4027@digraph.polyomino.org.uk> <534c2613-da1e-7b53-338c-2988b44b1b6b@redhat.com>
User-Agent: Alpine 2.21 (LSU 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-IsSubscribed: yes
X-SW-Source: 2019-05/txt/msg00153.txt.bz2

Hello Nick,

On Fri, 3 May 2019, Nick Clifton wrote:

>   * Usefulness
> 
>     This may be a bit contentious - but is the CTF format actually being
>     used anywhere, or likely to be used in the near future ?  If this is
>     a project that is just going to be used by a small group, or even just
>     a single company, then I am worried that the code will just bit rot 
>     away and not be actively maintained.

FWIW, I'd be looking forward to have CTF in our distro binaries shipped by 
default, it might obviate the need for separate -debuginfo packages, you'd 
get somewhat useful analysis capabilities even without them then.

So, I'm very happy about someone investing into getting CTF onto linux; I 
considered doing that myself on and off, just never could bring myself 
to start ;-)


Ciao,
Michael.