Hello,
On the latest beta, trap with an empty function work well ...
$ print ${.sh.version}
Version JM 93t+ 2010-03-05
$
Regards,
Yves
On Wed, Mar 31, 2010 at 1:45 PM, Dr. Werner Fink <[email protected]> wrote:
>
> On Mon, Mar 29, 2010 at 11:08:37AM +0200, Werner Fink wrote:
>> Hi,
>>
>> I've just become owner of a bug report reporting a flaky behaviour
>> in handling traps on SIGCHLD. For a simply test see
>>
>> ksh> echo ${sh.version}
>> Version JM 93t+ 2010-02-14
>> ksh> trap "" CHLD
>> let n=0; for d in $(seq 1 200); do if echo foo | grep bar; then echo oops
>> $((n++)); fi; done
>> bang 0
>> [...]
>> bang 177
>> ksh>
>>
>> and repeating the loop results in different numbers of reports
>> showing that there is a race as there should no report at all.
>>
>> Beside this setting the trap to something not empty works like
>>
>> ksh> trap ";" CHLD
>> let n=0; for d in $(seq 1 200); do if echo foo | grep bar; then echo oops
>> $((n++)); fi; done
>> ksh>
>>
>> which is very strange. It is very common to use an
>> empty string for traps used for ignoring signals, though.
>
> Are there any news?
>
> Werner
>
> --
> "Having a smoking section in a restaurant is like having
> a peeing section in a swimming pool." -- Edward Burr
> _______________________________________________
> ast-developers mailing list
> [email protected]
> https://mailman.research.att.com/mailman/listinfo/ast-developers
>
>
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
