Re: signal handling problem

[christos%astron.com@localhost (Christos Zoulas)]

In article <201007121550.23117.mark%ecs.vuw.ac.nz@localhost>,
Mark Davies  <mark%ecs.vuw.ac.nz@localhost> wrote:
>On Mon, 12 Jul 2010, Christos Zoulas wrote:
>> Yes, that is why I am asking. It seems that while pselect is
>> getting interrupted by presumably the sigchld signal, the sigchld
>> signal is not being posted to the process so the sigchld variable
>> is not set.
>
>Indeed.  Here is a ktrace -i for completeness:
>               [...]
> 15830      1 cnid_dbd CALL  fcntl(2,8,0xbfbfedf4)
> 15830      1 cnid_dbd RET   fcntl 0
> 15830      1 cnid_dbd CALL  close(2)
> 15830      1 cnid_dbd RET   close 0
> 15830      1 cnid_dbd CALL  exit(0)
>   460      1 cnid_metad RET   pselect -1 errno 4 Interrupted system 
>call
>   460      1 cnid_metad CALL  wait4(0xffffffff,0xbfbfee6c,1,0)
>   460      1 cnid_metad RET   wait4 15830/0x3dd6
>   460      1 cnid_metad CALL  close(4)
>   460      1 cnid_metad RET   close 0
>   460      1 cnid_metad CALL  wait4(0xffffffff,0xbfbfee6c,1,0)
>   460      1 cnid_metad RET   wait4 0
>   460      1 cnid_metad CALL  pselect(1,0xbfbfe8f4,0,0,0,0xbfbfee38)

Yup, the signal does not get posted. I would file a PR.

christos