You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I might have some misunderstanding here, so please correct me.
In dbg_logs.c:44 you might have a typo meaning >= instead of >. ATM I have to write jtagcore_set_logs_level(core, MSG_DEBUG + 1); to get debug messages.
What irritates me is the ordering of the message levels. If I say MSG_WARNING I normally only want warnings and more critical things like errors. ATM I become the info messages (and only them). Also MSG_DEBUG is higher as MSG_ERROR.
Wouldn't the order
Hello,
I might have some misunderstanding here, so please correct me.
In dbg_logs.c:44 you might have a typo meaning >= instead of >. ATM I have to write
jtagcore_set_logs_level(core, MSG_DEBUG + 1);
to get debug messages.What irritates me is the ordering of the message levels. If I say MSG_WARNING I normally only want warnings and more critical things like errors. ATM I become the info messages (and only them). Also MSG_DEBUG is higher as MSG_ERROR.
Wouldn't the order
and the test
if( jc->logs_level <= MSGTYPE )
make more sense?The text was updated successfully, but these errors were encountered: