Re: [gentoo-dev] Introduce global dmalloc USE flag?
On Mon, Jun 24, 2013 at 11:37 AM, Gilles Dartiguelongue wrote: > 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 ? > I think we already got a number of packages where that holds true. It was one of the reasons why I did my best to make sure people understand that debug symbols and nostrip should *not* be conflated with USE=debug. If I'm not mistaken, app-editors/nano[debug] is hardly usable. Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/
Re: [gentoo-dev] Introduce global dmalloc USE flag?
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 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)" > 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 Gentoo
Re: [gentoo-dev] Introduce global dmalloc USE flag?
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 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)" 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.
Re: [gentoo-dev] Introduce global dmalloc USE flag?
Le samedi 22 juin 2013 à 15:48 +0800, Dennis Lan (dlan) a écrit : > 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ł Górny wrote: > >> Dnia 2013-06-13, o godz. 09:35:54 "Dennis Lan (dlan)" > >> 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. -- Gilles Dartiguelongue Gentoo
Re: [gentoo-dev] Introduce global dmalloc USE flag?
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ł Górny wrote: >> Dnia 2013-06-13, o godz. 09:35:54 "Dennis Lan (dlan)" >> 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 > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlHDSyEACgkQ2ugaI38ACPAHUwEAqFFDyarLSE8I/k8eKBUibmxu > qZT2pnaaMj3nPEqrFxYBAIsIP8HAHR5mIaLBHKPiR6/oI/cxcu3h1XFodpbERO4t > =T2KX > -END PGP SIGNATURE- >
Re: [gentoo-dev] Introduce global dmalloc USE flag?
-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)" > 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? > 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 any particular benefit to USE="debug -dmalloc" ? Or USE="dmalloc - -debug" ? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlHDSyEACgkQ2ugaI38ACPAHUwEAqFFDyarLSE8I/k8eKBUibmxu qZT2pnaaMj3nPEqrFxYBAIsIP8HAHR5mIaLBHKPiR6/oI/cxcu3h1XFodpbERO4t =T2KX -END PGP SIGNATURE-
Re: [gentoo-dev] Introduce global dmalloc USE flag?
Dnia 2013-06-13, o godz. 09:35:54 "Dennis Lan (dlan)" 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? -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] Introduce global dmalloc USE flag?
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
