On 2/23/2019 1:42 PM, mugginsac wrote:
> About a month ago Zultron "fixed" a logging problem. He changed rtapi_print
> from:
>
> void rtapi_print(const char *fmt, ...) {
> va_list args;
> va_start(args, fmt);
> rtapi_msg_handler(RTAPI_MSG_ERR, fmt, args);
> va_end(args);
> }
>
> to:
> void rtapi_print(const char *fmt, ...) {
> va_list args;
> va_start(args, fmt);
> rtapi_msg_handler(RTAPI_MSG_ALL, fmt, args);
> va_end(args);
> }
>
> This appears to be what is causing the messages to show up when axis starts
> even though there is no error.
> However, they show up with an X in a red circle, so it sure looks like an
> error. Is there a way to fix the logging problem
> without making the user think there is an error???
If this is specific to the hal_pru_generic driver, the driver source
should probably be fixed. I wrote a fair amount of the driver code
before I really understood how the logging worked (esp. since
traditional LCNC drivers ran in kernel space).
If it's an issue that affects other drivers (esp. the hm2/mesa code),
then the "fix" should be reviewed and maybe changed.
--
Charles Steinkuehler
[email protected]
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
