A rapid sequence of (DEBUG,..), (PRINT..) or error messages can overrun the error channel queue between emctask and the user interface, as the queue full condition was not checked for. My inspect changes - i.e. the roparams.ngc file - triggered this bug.
The fix is here: http://git.mah.priv.at/gitweb/emc2-dev.git/shortlog/refs/heads/errorchannel-overrun-fix This takes care of all three message types. - Michael ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
