Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14696 > unrolled thread

Re: Segfault on recursive trap/kill

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Segfault on recursive trap/kill Mike Gerwitz <mtg@gnu.org> - 2018-10-07 13:21 -0400

#14696 — Re: Segfault on recursive trap/kill

[Multipart message — attachments visible in raw view] — view raw

On Sun, Oct 07, 2018 at 08:52:25 +0200, Valentin Bajrami wrote:
> As earlier expained, you are calling foo function recursively. To mitigate
> this behaviour you simple set FUNCNEST=<N> foo() { foo; }; foo where N
> denotes the number of nested functios to be called.

This is perfect and clear behavior, actually:

  $ FUNCNEST=10; foo() { foo; }; foo
  bash: foo: maximum function nesting level exceeded (10)

If bash were to set a default value for FUNCNEST then a useful error
would be provided rather than segfaulting (and possibly triggering a
coredump).  Of course, if bash itself is sharing a stack with the
interpreter, then it's hard to come up with a good predetermined value.

FUNCNEST doesn't seem to work with the issue of recursive traps, though
(understandably).

-- 
Mike Gerwitz

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web