From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2983A1381F3 for ; Thu, 13 Jun 2013 02:01:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EE1A4E0869; Thu, 13 Jun 2013 02:01:01 +0000 (UTC) Received: from mail-vb0-f42.google.com (mail-vb0-f42.google.com [209.85.212.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0379EE084C for ; Thu, 13 Jun 2013 02:01:00 +0000 (UTC) Received: by mail-vb0-f42.google.com with SMTP id i3so6266456vbh.15 for ; Wed, 12 Jun 2013 19:01:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=RyJQXzrC0lP0FiKT70cdrkvkw/j/LRmHyqby12rjJts=; b=LgrUPvYTqICRE73b7lHNnFNbImCITn9SSbef4jykwDIhW8DxzLc0fXS0R15DppsX8t OXJAFtalhFFGirjCG+BBl5Xej5/Zh9qcvWi84ksV0UcbWCS6OswSxzr5zGsSSvZbl5nR Fm/jk/NLwXgtBPF4OHYj6ADkL2Tlp7ISsfpXREA4zU9QBIO0x/U0MsitnwhuV+JBVi2c hQI0T4OJZyKyYaTJ22oOiuaRMK8YZPBUBy9C8SpZpGBp+1+SzNCTFE3ApC/j7U9s2Xhs NPjFXoj5yA+D4FRx8Dcw1L/VJOzqoiCuu9iZSFAFcRzWI/pxaPNxCl2L73uItLFpoCze 4DuQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.58.215.200 with SMTP id ok8mr10773622vec.21.1371088859955; Wed, 12 Jun 2013 19:00:59 -0700 (PDT) Received: by 10.58.44.195 with HTTP; Wed, 12 Jun 2013 19:00:59 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Jun 2013 14:00:59 +1200 Message-ID: Subject: Re: [gentoo-dev] Introduce global dmalloc USE flag? From: Kent Fredric To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a11c39f087414ef04deff8063 X-Archives-Salt: 4ca8a33c-2526-4125-a936-a9d570fb5626 X-Archives-Hash: d46fc0a157881cb7734aa65831c49fdb --001a11c39f087414ef04deff8063 Content-Type: text/plain; charset=UTF-8 On 13 June 2013 13:35, Dennis Lan (dlan) wrote: > HI ALL: > Is it ok to introduce USE=dmalloc global flag? description as following > "dmalloc - Enable debugging with the dmalloc library" > > current consumers: > 1) net-fs/autofs > 2) net-misc/directvnc > 3) sci-biology/yass > > also > 4) app-admin/conserver > 5) net-nds/ypbind > 6) net-fs/samba > 7) net-analyzer/scli > 8) net-analyzer/traceproto > 6) net-misc/siproxd > > use dmalloc but controlled under USE=debug > > Dennis Lan > > Questions for clarity: 1. I haven't used dmalloc before, what does this use flag do for me? 2. How does this use flag change the built binaries? does it: a) make no user visible changes, but adds code instrumentation paths which can only be seen/understood with a special visualiser b) add output to TTY for the built binary? etc. I'm not arguing against global USE for it, I'm just asking for a USE description that is more meaningful. ie, alternatives might be: "Add runtime debug output via the dmalloc library" or "Add runtime instrumentation for the dmalloc debugger", or something like that. Because if it were case a), then I might be inclined to turn it on arbitrarily ( depending on how much it impacts performance ), just in case I happen to need it one day. But if it were case b), I'd be inclined not to turn it on arbitrarily, because I can see that would be irritating =) -- Kent --001a11c39f087414ef04deff8063 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 13 June 2013 13:35, Dennis Lan (dlan) <dennis.yxun@gmail.com>= ; wrote:

Dennis Lan


Questions for clarity:

1. I hav= en't used dmalloc before, what does this use flag do for me?
2. How= does this use flag change the built binaries? does it:
=C2=A0=C2=A0 a) = make no user visible changes, but adds code instrumentation paths which can= only be seen/understood with a special visualiser
=C2=A0=C2=A0 b) add output to TTY for the built binary? etc.

I'm= not arguing against global USE for it, I'm just asking for a USE descr= iption that is more meaningful.

ie, alternatives migh= t be: "Add runtime debug output via the dmalloc library" or "= ;Add runtime instrumentation for the dmalloc debugger", or something l= ike that.

Because if it were case a), then I might be inclined to turn it on arbi= trarily ( depending on how much it impacts performance ), just in case I ha= ppen to need it one day.=C2=A0 But if it were case b), I'd be inclined = not to turn it on arbitrarily, because I can see that would be irritating = =3D)


--
Kent

--001a11c39f087414ef04deff8063--