Re: Segfault on recursive trap/kill

2018-10-07 Thread Mike Gerwitz
On Sun, Oct 07, 2018 at 09:42:01 +0700, Robert Elz wrote: > I expect that if you did look, you'd probably find that while > technically the former, it isn't a reference to some wild pointer, > but rather simply growing the stack until the OS says "no more" > and returns a SIGSEGV instead af allocat

Re: Segfault on recursive trap/kill

2018-10-07 Thread Mike Gerwitz
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= foo() { foo; }; foo where N > denotes the number of nested functios to be called. This is perfect and clear behavio

Re: Segfault on recursive trap/kill

2018-10-07 Thread Valentin Bajrami
Hi Mike, As earlier expained, you are calling foo function recursively. To mitigate this behaviour you simple set FUNCNEST= foo() { foo; }; foo where N denotes the number of nested functios to be called. Op zo 7 okt. 2018 07:57 schreef Mike Gerwitz : > Hey, Bob! > > On Sat, Oct 06, 2018 at 22:4