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 A78921381F3 for ; Sat, 22 Jun 2013 07:48:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DBF79E0B03; Sat, 22 Jun 2013 07:48:53 +0000 (UTC) Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0ACC2E0AFF for ; Sat, 22 Jun 2013 07:48:52 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id wc20so9355198obb.18 for ; Sat, 22 Jun 2013 00:48:52 -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:content-transfer-encoding; bh=1Y2lrB427RBJW0ZoRaMPN5iwD7MKeYyjece+rgn93Uc=; b=MXFvhtYTpG+fYfyioNWjfsIppsYWJZHS1Ob00iyVDRQOhmXgjFKo/+R5H0PiWdhFlU bnvrxNaNnePf7V8sl4Z7KCoCzf4LKYs6qj685d6809tlvqQpLpqnmi4dJMvFs/SNUqmn s8/R9iWE699FXvVVzlm2VhJoly66pWF8tR//0HXXzgb+3XPVgIULujbKFk6eOua4TaVw SJQJmdPkda2KkeUc9UAxefzhiP6XZXzfkoRYDA2sAXZj1E/EQAqBo6td50wqa4+0eNaa fA1hna3d0CCCyZrCAjq2B+B8BsWbjm/bo0VDAFtk/jZxqlkdwEfjEk88t2JSyldO2asf rFJQ== 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.182.66.77 with SMTP id d13mr2206026obt.32.1371887332134; Sat, 22 Jun 2013 00:48:52 -0700 (PDT) Received: by 10.60.65.68 with HTTP; Sat, 22 Jun 2013 00:48:52 -0700 (PDT) In-Reply-To: <51C34B21.2040504@gentoo.org> References: <20130613070520.5e919998@gentoo.org> <51C34B21.2040504@gentoo.org> Date: Sat, 22 Jun 2013 15:48:52 +0800 Message-ID: Subject: Re: [gentoo-dev] Introduce global dmalloc USE flag? From: "Dennis Lan (dlan)" To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 89656a16-0497-4d87-8057-4bea08581dd9 X-Archives-Hash: 732e1220031c0cb6eed2cf94637d4ba9 On Fri, Jun 21, 2013 at 2:34 AM, Ian Stakenvicius wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 13/06/13 01:05 AM, Micha=C5=82 G=C3=B3rny wrote: >> Dnia 2013-06-13, o godz. 09:35:54 "Dennis Lan (dlan)" >> napisa=C5=82(a): >> >>> 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=3Ddebug >> >> Do those use USE=3Ddebug solely for dmalloc or does it imply other >> stuff? Therefore: will it be possible to use USE=3Ddmalloc in those >> packages? HI mgorny, as I look into those ebuilds all of them use the USE=3Ddebug flag for dmalloc only, not for other debugging control so, as your second question, of course it's possible to switch to USE=3Ddma= lloc >> > > and to follow up, if we assume that USE=3D"debug" does more than just > build the package against the dmalloc lib (which is likely), is there Yes, if this case exist.. then the separation would be good > any particular benefit to USE=3D"debug -dmalloc" ? Or USE=3D"dmalloc > - -debug" ? > I'm not sure, probably the befefits would be that we can have more accurate/explicit control, USE=3D"dmalloc" is for debugging memory usage stuff (allocation, free, fence-post overwritten control) and USE=3Ddebug for other stuff? This is a slightly improvement, but I'm also totally fine to keep current state as it is.. no big deal > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlHDSyEACgkQ2ugaI38ACPAHUwEAqFFDyarLSE8I/k8eKBUibmxu > qZT2pnaaMj3nPEqrFxYBAIsIP8HAHR5mIaLBHKPiR6/oI/cxcu3h1XFodpbERO4t > =3DT2KX > -----END PGP SIGNATURE----- >