Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] M810-M819 G-code macros: Makro invokes other macro crashes Marlin #20919

Closed
rubienr opened this issue Jan 29, 2021 · 2 comments
Closed

Comments

@rubienr
Copy link
Contributor

rubienr commented Jan 29, 2021

Bug Description

When running a macro that calls another macro Marlin crashes. Tested with bugfix-2.0.x at revision ac82dc4.

Configuration Files

configuration.zip

Steps to Reproduce

  1. Define macro M810, then
  2. define a second macro M811 that calls M810, and
  3. call M811.

Example input:

M810 M400
M811 M810 | M400 | M810
M811

Example output from Octoprint console:

Send: M810 M400
Recv: ok P63 B15
Send: M811 M810 | M400 | M810
Recv: ok P63 B15
...
Recv:  M400
Recv:  M810"
Recv: echo:Unknown command: "
Recv:  M400
Recv:  M810"
Recv: echo:Unknown command: "
Recv:  M400
Recv:  M810"
Recv: echo:Unknown command: "
...
; this lines repeat until Marlin reboots

Expected behavior:
M811 calls M810 then M400 then M810.

Actual behavior:
Looks like M811 lets M810 being re-defined as "M400 | M810", then M810 is called.

Counter Example:

M810 M400
M811 M400 | M400 | M810
M811 ; ok
@github-actions
Copy link

github-actions bot commented Mar 1, 2021

This issue has had no activity in the last 30 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 7 days.

@github-actions
Copy link

github-actions bot commented May 7, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant