Fix garbage in C/python log messages in CMA

[Alan-R]

Here are some sample outputs:

Aug  3 18:35:39 servidor <80><93>þk<8a>^?[23135]: DEBUG: _netio_setsockbufsize.278: trying to set input buffer size to 10485760
Aug  3 18:35:39 servidor <80><93>þk<8a>^?[23135]: DEBUG: _netio_setsockbufsize.278: trying to set output buffer size to 1048576

The process ID (23235) is the parent process for the CMA:

assimil+ 23135 23132  0 18:35 pts/1    00:00:05 python ./cma.py --debug 2 --erasedb --foreground

This is very consistent and happens every time we start the CMA.
There are corresponding log messages from the CMA itself, and they look just fine:

Aug  3 18:35:55 servidor cma INFO: Socket input buffer size:  20971518
Aug  3 18:35:55 servidor cma INFO: Socket output buffer size: 2097150

[Alan-R]

The code generating this message is:

DEBUGMSG2("%s.%d: trying to set %sput buffer size to %d", __FUNCTION__, __LINE__
	,	 (forinput ? "in" : "out"), retval);

DEBUGMSG2 is defined as:

#define DEBUGMSG2(...) DEBUGMSGn(2, __VA_ARGS__)

and DEBUGMSGn is defined as:

#define DEBUGMSGn(n, ...) {if (DEBUG >= (n)) {g_debug(__VA_ARGS__);};}

Which comes down to g_debug from glib2.
This used to work.
Which makes me think maybe it's a change in Glib.
I suspect things related to g_log_writer_default() - which formats things suitable for the systemd journal.