Back
[14:16:23] <bpuk> Hmm... anyone know where logDebug outputs to?
[14:32:12] <pcw_home> I dont know but RTAI based systems log most errors to the kernel log (dmesg to read)
[14:32:40] <bpuk> that's where I thought it logged to, but nope.
[14:32:47] <bpuk> will keep hunting
[14:44:21] <jepler> looks like inifile items are related
[14:44:22] <jepler> if(NULL != (inistring = inifile.Find("LOG_LEVEL", "RS274NGC")))
[14:44:25] <jepler> if(NULL != (inistring = inifile.Find("LOG_FILE", "RS274NGC")))
[16:38:57] <bpuk> jepler: I've tried changing those, nothing at all gets put into that file on my test system
[18:08:19] <jepler> bpuk: darn, that's all I've been able to guess :(
[18:35:04] <jepler> bpuk:so I just basically made _logDebug unconditionally fprintf(stderr, fmt "\n", ## args);
[18:35:09] <jepler> and that gets me debug info in the terminal
[18:35:25] <jepler> don't forget, you can attach to milltask or rs274 with gdb to debug too
[18:35:36] <jepler> e.g., after starting linuxcnc, gdb -p `pidof milltask`
[18:35:46] <jepler> or if you want to run rs274, gdb --args rs274 -g test.ngc