Re: Bug with traps and exit

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Peter Stephenson wrote on Fri, Dec 13, 2019 at 14:49:40 +0000:
> As you know, getting anyone interested in looking at things is very
> difficult.  I'm taking more of a back seat myself, unless I can see
> something glaring.  Anyone is more than welcome to jump in while
> the old guard is still looking on to help.

I don't know about others, but I'm not even sure where to begin fixing this.
I can find the code handling traps easily enough ('intrap', etc), and I know
where the code handling functions is (doshfunc()), but how to proceed?  Would
the right fix be to add some code in the end of runshfunc(), after
unqueue_signals(), that checks whether a trap has been executed and called
'exit'…?

If anyone else want to jump in, please do!

Cheers,

Daniel