From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Subject: Re: [PATCH] mk: add support for gdb debug info generation
Date: Tue, 23 Jun 2015 08:39:38 +0100
Message-ID: <55890D3A.109@intel.com>
References: <1434749378-8578-1-git-send-email-cchemparathy@ezchip.com>
 <5587BCE9.4000809@intel.com> <5587BFA7.2000206@netinsight.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
To: =?windows-1252?Q?Simon_K=E5gstr=F6m?= <simon.kagstrom@netinsight.net>,
 dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id EA212C674
 for <dev@dpdk.org>; Tue, 23 Jun 2015 09:39:40 +0200 (CEST)
In-Reply-To: <5587BFA7.2000206@netinsight.net>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 22/06/2015 08:56, Simon K=E5gstr=F6m wrote:
> On 2015-06-22 09:44, Gonzalez Monroy, Sergio wrote:
>> On 19/06/2015 22:29, Cyril Chemparathy wrote:
>>> From: Cyril Chemparathy <cchemparathy@tilera.com>
>>>
>>> It is often useful to build with debug enabled, we add a config
>>> (CONFIG_RTE_TOOLCHAIN_DEBUG) to do so.
>>>
>>>    +ifeq ($(CONFIG_RTE_TOOLCHAIN_DEBUG),y)
>>> +TOOLCHAIN_CFLAGS +=3D -g -ggdb
>>> +TOOLCHAIN_LDFLAGS +=3D -g -ggdb
>>> +endif
>> I don't think you need to modify the makefiles and introduce a new
>> compile time option for this.
>> The same result can be easily achieved by setting EXTRA_CFLAGS in the
>> command line. ie:
>>      $ make install T=3Dx86_64-native-linuxapp-gcc EXTRA_CFLAGS=3D'-g =
-ggdb'
> Why isn't -g standard though? The binaries should/will anyhow be
> stripped when used for production - but debugging information should be
> useful when analysing crashes.
I guess you could argue that, to always build with debug info then strip=20
it down.
You would need another flag to strip debug info for production, or leave=20
it for debugging.

In my opinion is not worth it, but it you feel strongly about it you can=20
submit patches and
let the community decide.

Sergio
> // Simon
>