Date: Wed, 09 Nov 2022 15:07:09 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 267527] bash crashes with segfault if LC_CTYPE or LC_ALL not set Message-ID: <bug-267527-7788-df2EtjKAdq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267527-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-267527-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267527 Michal <michal.berger@intel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michal.berger@intel.com --- Comment #2 from Michal <michal.berger@intel.com> --- Hit that as well. Logging in via serial (tty{,S}* or through getty in gener= al) may be indeed troublesome, for ssh there's still a silly workaround, e.g. ssh -t foo@bar sh $ LC_CTYPE=3D bash -l though interestingly this affects bash only in interactive|login mode (so a= ny potential bash scripts that are doing some work shouldn't be affected) but = what seems to be indicative of what was mentioned on the forum (i.e. issue coming from the readline). As: $ bash -c 'read -rp 'oops: ' # this works $ bash -c 'read -erp 'oops: ' # this doesn't so, actually, scripts can be affected when they do use readline (but outsid= e of the interactive context it would be quite uncommon I think). (In reply to ralph from comment #0) --=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-267527-7788-df2EtjKAdq>