That doesn't ring a bell. Does it happen with every configuration (e.g., configs/sim/axis/axis.ini) or just with certain ones?
Is there any more information, such as python source code line numbers, shown? Run from the terminal and/or check the linuxcnc_*.txt files in your home directory. If the locations and byte values vary from run to run, it feels to me like it may be an uninitialized memory sort of bug, except that it's harder to create those in Python than in C(++). Of course, if you've determined that it depends on named parameters then it is probably happening in the gcode interpreter itself. If you can figure out what process it's coming from, arrange to run it under valgrind. This is an excellent tool for diagnosing access to uninitialized memory. Jeff ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
