2010-10-27, 01:46
I was just perusing the cmyth library. I noticed this:
/trunk/xbmc/lib/cmyth/include
Those stderr line are what makes it difficult to redirect output to a file. Why not output on stdout? Is there a purpose to output DEBUG lines on stderr instead of stdout?
I can see outputting nearly everything in proginfo.c to stderr, but connection, freespace... most of the rest of them should be stdout because they are valuable debug information and not just tons of factual information about a recording.
Still compiling with the options you require.
/trunk/xbmc/lib/cmyth/include
Code:
mvp_dbg(mvp_debug_ctx_t *ctx, int level, char *fmt, va_list ap)
{
if (!ctx) {
return;
}
if ((ctx->selector && ctx->selector(level, ctx->cur_level)) ||
(!ctx->selector && (level < ctx->cur_level))) {
fprintf(stderr, "(%s)", ctx->name);
vfprintf(stderr, fmt, ap);
}
}
I can see outputting nearly everything in proginfo.c to stderr, but connection, freespace... most of the rest of them should be stdout because they are valuable debug information and not just tons of factual information about a recording.
Still compiling with the options you require.