Date: Wed, 09 Feb 2022 11:50:40 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261819] ports-mgmt/portfmt: portclippy will core dump for unknown command line options Message-ID: <bug-261819-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261819 Bug ID: 261819 Summary: ports-mgmt/portfmt: portclippy will core dump for unknown command line options Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: tobik@freebsd.org Reporter: martin@waschbuesch.de Assignee: tobik@freebsd.org Flags: maintainer-feedback?(tobik@freebsd.org) portclippy knows only one command line option: --strict However, the behavior when giving unknown options seems broken: While unknown options with just one '-' produce output like this: root@dev:~# portclippy -blub portclippy: invalid option -- b usage: portclippy [--strict] [Makefile] If you give anything other than --strict using '--', it will just crash: root@dev:~# portclippy --blub Bus error (core dumped) (Arguably, even in the first instance, it seems weird the message complains about the command line as if only one letter had been given.) I have only tested this on 13.0-RELEASE on amd64. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261819-7788>