Skip to content

sim/touchy: disable EMC_DEBUG_TASK_ISSUE logging (DEBUG=0)#4073

Open
grandixximo wants to merge 1 commit into
LinuxCNC:masterfrom
grandixximo:fix/touchy-debug-ascii-nml
Open

sim/touchy: disable EMC_DEBUG_TASK_ISSUE logging (DEBUG=0)#4073
grandixximo wants to merge 1 commit into
LinuxCNC:masterfrom
grandixximo:fix/touchy-debug-ascii-nml

Conversation

@grandixximo
Copy link
Copy Markdown
Contributor

touchy.ini was the only sim config shipping a non-zero DEBUG (0x10 =
EMC_DEBUG_TASK_ISSUE). That makes task log every issued NML command as an
ASCII string via emcCommandBuffer->msg2str(), which instantiates a
CMS_DISPLAY_ASCII_UPDATER and prints its "may not function properly"
banner on startup. The emcCommand buffer is correctly xdr; the ASCII
updater is only a transient string helper for the debug log.

Set DEBUG = 0 (matching axis and gmoccapy). No functional change.

Surfaced in the ui-smoke review, PR #4054.

Test: touchy sim under xvfb, banner no longer printed, GUI starts normally.

touchy.ini was the only sim config shipping a non-zero DEBUG (0x10 =
EMC_DEBUG_TASK_ISSUE). That flag makes task log every issued NML command
as an ASCII string via emcCommandBuffer->msg2str(), which lazily creates
a CMS_DISPLAY_ASCII_UPDATER and prints its scary 'may not function
properly due to range limitations' banner on startup.

The emcCommand buffer is correctly xdr-encoded; the ASCII updater is only
a temporary string-conversion helper for the debug log. Setting DEBUG=0
(matching axis and gmoccapy sims) stops the task-issue logging and the
spurious banner. No functional change to touchy.

Surfaced by the ui-smoke tests (LinuxCNC#4054).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants