Runtime option for debug output?

[Bart Cerneels]

And if possible, selective runtime debugging per sub-system. This would make
developing and debugging parts of Amarok easier.

2007/8/3, Nikolaj Hald Nielsen <nhnfreespirit at gmail.com>:
>
> I think it would be really useful.
>
> I am all for the "give it a try and see how it goes" approach as
> opposed to thinking too much about it and never doing anything! :-)
>
>
>
> On 8/3/07, Mark Kretschmann <kretschmann at kde.org> wrote:
> > This happened today on #amarok:
> >
> > 09:24 < Kebianizao> markey: is there a verbose option for amarokapp?
> > 09:25 < markey> --enable-debug=full
> > 09:25 < markey> compile time
> > 09:25 < Kebianizao> do you really have to rebuild to get that?
> > 09:25 < Kebianizao> :O
> >
> > Which makes me wonder (again) if we shouldn't make our debug output a
> > runtime option, e.g. "amarok --debug". We've discussed this briefly
> > some time ago, but no decision was reached.
> >
> > I think the advantages of this approach are obvious (no rebuilding
> > needed), so I'm wondering about the disadvantages. It might make the
> > binary somewhat bigger, but that's all I can think of.
> >
> > --
> > Mark
> > _______________________________________________
> > Amarok-devel mailing list
> > Amarok-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/amarok-devel
> >
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/amarok-devel/attachments/20070803/9352867c/attachment.html