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

Segmentation fault when running with "--help-fff" or "--help-sla" options #11060

Closed
2 tasks done
JohnnyB83 opened this issue Jul 31, 2023 · 4 comments
Closed
2 tasks done

Comments

@JohnnyB83
Copy link

Description of the bug

Version
PrusaSlicer-2.6.0+linux-x64

Operating system type + version
Debian GNU/Linux 11 (bullseye)
3D printer brand / version + firmware version (if known)
Original Prusa i3 MK3S+ (firmware version not applicable to problem)

Behavior
Run prusa-slicer with either the ---help-fff or ---help-sla options in the command line
Once the Misc options section is displayed on the screen, a segmentation fault occurs and prusa-slicer exits
Error message in console after running the command: qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault

Project file & How to reproduce

How to reproduce:
Run prusa-slicer --help-fff as a CLI command

config.ini.zip

Screenshot 2023-07-30 at 6 39 44 PM

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.6.0+linux-x64

Operating system

Debian GNU/Linux 11 (bullseye)

Printer model

Original Prusa i3 MK3S+

combolek added a commit to combolek/PrusaSlicer that referenced this issue Sep 2, 2023
Added missing null pointer check in ConfigDef::print_cli_help()
@combolek
Copy link
Contributor

combolek commented Sep 2, 2023

This is also reproducible in the latest master. I submitted PR #11234 to fix it.

@zenda97
Copy link

zenda97 commented Sep 4, 2023

Reproduced, thank you for the report.
SPE-1859

@bubnikv
Copy link
Collaborator

bubnikv commented Sep 5, 2023

Thanks, merged. It will be fixed in the 2.6.1 final.

@bubnikv bubnikv closed this as completed Sep 5, 2023
@mkoistinen
Copy link

Looks like this also fixed issue #10950. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants