output to stdout/stderr

[biebl]

Hi,

it would be nice, if the output of kdesvn to stdout/stderr could be configurable and more fine grained.

Imho only critical errors should be printed to stderr, info/diag/debug messages should be off by default.

See also the corresponding Debian bug  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431616

[alwin]

These are all output of kDebug() calls - them may switched off I thought on compile time or later with the kdebugdialog.

I may switch over all debug output to debug number 9510 which is called "kdevplatform (subversion)" and may match kdesvn :) (and include a hint into handbook/faq)

so users may easy switch off it. what about?

[Michael]

I think I'd prefer a separate debug number, which is tied directly to the kdesvn program name.

If I search for svn or subversion, I get

7128 kio_svn 9510 kdevplatform (subversion)

I guess they are coming from the KDE4 plattform, not quite sure. Point is, I wouldn't immediately recognize which one to modify. Is kdesvn currently using the generic (0) debug number?

What do you think about changing the defaults (only debug messages going to stdout)?

[alwin]

Replying to Michael:

I think I'd prefer a separate debug number, which is tied directly to the kdesvn program name.

It can not assigned outside kdelibs.

7128 kio_svn 9510 kdevplatform (subversion)

I guess they are coming from the KDE4 plattform, not quite sure. Point is, I wouldn't immediately recognize which one to modify. Is kdesvn currently using the generic (0) debug number?

Yes its using the generic. And using an own number makes no sense, users hadn't a real chance switch it off 'cause the kdebugdialog doesn't know something about. These numbers are defined inside kdelibs itself and looks ok.

What do you think about changing the defaults (only debug messages going to stdout)?

There are only debug-messages from development, I have no reasons doing more. I thought them will switched off in release-builds with -DKDE_NO_DEBUG_OUTPUT.

Yes, of course I'll reduce the debug outputs, most of them aren't needed this moment.

[mbiebl@…]

Replying to alwin:

Replying to Michael:

I think I'd prefer a separate debug number, which is tied directly to the kdesvn program name.

It can not assigned outside kdelibs.

Hm, ok. Seems you are right. Just found $prefix/share/config/kdebug.areas

As  http://lists.kde.org/?l=kde-devel&m=106607933724723&w=2 explicitely recommends to use 0 (generic) for external apps, I guess I'd follow this recommendation and not change the debug area.

7128 kio_svn 9510 kdevplatform (subversion)

I guess they are coming from the KDE4 plattform, not quite sure. Point is, I wouldn't immediately recognize which one to modify. Is kdesvn currently using the generic (0) debug number?

Yes its using the generic. And using an own number makes no sense, users hadn't a real chance switch it off 'cause the kdebugdialog doesn't know something about. These numbers are defined inside kdelibs itself and looks ok.

Either way (using 0 or 9510), I think adding a note to the faq how to switch off the messages via kdedebugdialog is a good idea.

What do you think about changing the defaults (only debug messages going to stdout)?

Argh, I wanted to say: *no* debug messages on stdout by default. But afaics that is not possible with kDebug, as this is a global configuration and not per app.

There are only debug-messages from development, I have no reasons doing more. I thought them will switched off in release-builds with -DKDE_NO_DEBUG_OUTPUT.

Yes, of course I'll reduce the debug outputs, most of them aren't needed this moment.

[mbiebl@…]

I've seen you changed the debug area. I thought this might be of interet to you:  http://www.kdedevelopers.org/node/3171

[alwin]

Replying to mbiebl@gmail.com:

I've seen you changed the debug area. I thought this might be of interet to you:  http://www.kdedevelopers.org/node/3171

ah, wonderful did it in commit r1757. Debug output is reduced, so I close this bug (entry into faq follows)

[anonymous]

Replying to alwin:

Replying to mbiebl@gmail.com:

I've seen you changed the debug area. I thought this might be of interet to you:  http://www.kdedevelopers.org/node/3171

ah, wonderful did it in commit r1757.

I'd also change kDebug(9510) back to kDebug.

Debug output is reduced, so I close this bug (entry into faq follows)

Not quite. I still get quite some output like:

svn_cmdline_init done QLayout: Attempting to add QLayout "" to SvnLogDlgImp? "logdialog", which already has a layout

That seems to be a bug somewhere in the code

The key is now: logmain-logcache Insert into map Getting headrev Getting headrev done

Most of it seems to come from svnqt, which uses qDebug...