Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Andreas Schwab Newsgroups: gnu.bash.bug Subject: Re: A possible bug on autocompletion after setting FUNCNEST level Date: Mon, 08 Oct 2018 14:15:15 +0200 Lines: 29 Approved: bug-bash@gnu.org Message-ID: References: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: usenet.stanford.edu 1539000929 9712 208.118.235.17 (8 Oct 2018 12:15:29 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: Valentin Bajrami Envelope-to: bug-bash@gnu.org X-Virus-Scanned: by amavisd-new at test-mx.suse.de X-Yow: Don't hit me!! I'm in the Twilight Zone!!! In-Reply-To: (Valentin Bajrami's message of "Mon, 8 Oct 2018 14:06:39 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 195.135.220.15 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14699 On Okt 08 2018, Valentin Bajrami wrote: > This is some kind of a follow up on "Segfault on recursive trap/kill" > reported by Mike Grewitz. > > After setting FUNCNEST and the listing a file or using 'vi filname[TAB]' a > bug is triggered. > > This is how I could reproduce this: > > f3d0r4:~/FOO# FUNCNEST=4 > > f3d0r4:~/FOO# ls > procps-ng-3.3.12-3.fc28.src.rpm > procps-ng-3.3.12-pmap-all-lines-twice.patch procps-ng-3.3.12.tar.xz > procps-ng-3.3.14-CVE-2018-1124.patch procps-ng.spec README.md README.top > > f3d0r4:~/FOO# vi pr-bash: __reassemble_comp_words_by_ref: maximum function > nesting level exceeded (4) In which way is this a bug? AFAICT, FUNCNEST is doing its job. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."