From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Introduce global dmalloc USE flag?
Date: Mon, 24 Jun 2013 12:37:14 +0200 [thread overview]
Message-ID: <1372070234.19250.6.camel@gilles.gandi.net> (raw)
In-Reply-To: <51C80BDE.90600@gentoo.org>
Le lundi 24 juin 2013 à 12:05 +0300, Samuli Suominen a écrit :
> On 24/06/13 11:54, Gilles Dartiguelongue wrote:
> > Le samedi 22 juin 2013 à 15:48 +0800, Dennis Lan (dlan) a écrit :
> >> On Fri, Jun 21, 2013 at 2:34 AM, Ian Stakenvicius <axs@gentoo.org> wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA256
> >>>
> >>> On 13/06/13 01:05 AM, Michał Górny wrote:
> >>>> Dnia 2013-06-13, o godz. 09:35:54 "Dennis Lan (dlan)"
> >>>> <dennis.yxun@gmail.com> napisał(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=debug
> >>>>
> >>>> Do those use USE=debug solely for dmalloc or does it imply other
> >>>> stuff? Therefore: will it be possible to use USE=dmalloc in those
> >>>> packages?
> >>
> >> HI mgorny, as I look into those ebuilds
> >> all of them use the USE=debug flag for dmalloc only, not for other
> >> debugging control
> >> so, as your second question, of course it's possible to switch to USE=dmalloc
> >>
> >>>>
> >>>
> >>> and to follow up, if we assume that USE="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="debug -dmalloc" ? Or USE="dmalloc
> >>> - -debug" ?
> >>>
> >>
> >> I'm not sure, probably the befefits would be that we can have more
> >> accurate/explicit control,
> >> USE="dmalloc" is for debugging memory usage stuff (allocation, free,
> >> fence-post overwritten control)
> >> and USE=debug for other stuff?
> >>
> >> This is a slightly improvement, but I'm also totally fine to keep
> >> current state as it is.. no big deal
> >
> > Reading this thread, looks to me like these dmalloc USE should be moved
> > to debug, unless it has no runtime impact on usual speed, etc.
> >
>
> It does. In most often cases building against dmalloc makes the
> application/library completely unusable, and building it against dmalloc
> is intended for the developer of the application.
> Separated USE=dmalloc is the only sane way to approach it.
To be clear, the justification of USE=dmalloc being separated from
USE=debug is that it is so "intrusive" than anyone excepts a developer
would find it too cumbersome to attempt to debug a problem with the
application ?
If that is the case, maybe the USE flag description should mention that
so it is not enabled lightly.
--
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo
next prev parent reply other threads:[~2013-06-24 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 1:35 [gentoo-dev] Introduce global dmalloc USE flag? Dennis Lan (dlan)
2013-06-13 2:00 ` Kent Fredric
2013-06-13 5:05 ` Michał Górny
2013-06-20 18:34 ` Ian Stakenvicius
2013-06-22 7:48 ` Dennis Lan (dlan)
2013-06-24 8:54 ` Gilles Dartiguelongue
2013-06-24 9:05 ` Samuli Suominen
2013-06-24 10:37 ` Gilles Dartiguelongue [this message]
2013-06-24 10:47 ` Diego Elio Pettenò
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1372070234.19250.6.camel@gilles.gandi.net \
--to=eva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox