* Values for SigBlk and SigIgn are zero in /proc/$$/status
@ 2022-03-01 5:35 Ken SATO
2022-03-01 11:06 ` Corinna Vinschen
0 siblings, 1 reply; 5+ messages in thread
From: Ken SATO @ 2022-03-01 5:35 UTC (permalink / raw)
To: cygwin
Hello,
When I run the following command, the values for SigBlk and SigIgn are zero.
How can I get the correct value?
$ cat /proc/$$/status
Name: bash
State: S (sleeping)
Tgid: 1553
Pid: 1553
PPid: 1552
Uid: 197609 197609 197609 197609
Gid: 197121 197121 197121 197121
VmSize: 6144 kB
VmLck: 0 kB
VmRSS: 8960 kB
VmData: 2432 kB
VmStk: 0 kB
VmExe: 64 kB
VmLib: 4416 kB
SigPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
$
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Values for SigBlk and SigIgn are zero in /proc/$$/status
2022-03-01 5:35 Values for SigBlk and SigIgn are zero in /proc/$$/status Ken SATO
@ 2022-03-01 11:06 ` Corinna Vinschen
2022-03-01 19:46 ` Corinna Vinschen
0 siblings, 1 reply; 5+ messages in thread
From: Corinna Vinschen @ 2022-03-01 11:06 UTC (permalink / raw)
To: cygwin
On Mar 1 14:35, Ken SATO wrote:
> Hello,
>
> When I run the following command, the values for SigBlk and SigIgn are zero.
> How can I get the correct value?
You can't. We don't have the information readily available without
asking the process itself. While we have a communication mechanism
in place for stuff like that, it's not used yet for signal info.
It's something we can think about for 3.4, though.
Corinna
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Values for SigBlk and SigIgn are zero in /proc/$$/status
2022-03-01 11:06 ` Corinna Vinschen
@ 2022-03-01 19:46 ` Corinna Vinschen
2022-03-02 3:47 ` Ken SATO
0 siblings, 1 reply; 5+ messages in thread
From: Corinna Vinschen @ 2022-03-01 19:46 UTC (permalink / raw)
To: cygwin
On Mar 1 12:06, Corinna Vinschen wrote:
> On Mar 1 14:35, Ken SATO wrote:
> > Hello,
> >
> > When I run the following command, the values for SigBlk and SigIgn are zero.
> > How can I get the correct value?
>
> You can't. We don't have the information readily available without
> asking the process itself. While we have a communication mechanism
> in place for stuff like that, it's not used yet for signal info.
>
> It's something we can think about for 3.4, though.
I had a few spare cycles today so I took a stab at it and implemented
it. I uploaded new developer snapshots to https://cygwin.com/snapshots/,
please give it a try.
Thanks,
Corinna
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Values for SigBlk and SigIgn are zero in /proc/$$/status
2022-03-01 19:46 ` Corinna Vinschen
@ 2022-03-02 3:47 ` Ken SATO
2022-03-02 9:51 ` Corinna Vinschen
0 siblings, 1 reply; 5+ messages in thread
From: Ken SATO @ 2022-03-02 3:47 UTC (permalink / raw)
To: cygwin
Tue, 1 Mar 2022 20:46:54 +0100
Corinna Vinschen wrote:
> I had a few spare cycles today so I took a stab at it and implemented
> it. I uploaded new developer snapshots to https://cygwin.com/snapshots/,
> please give it a try.
Thank you for providing the snapshot.
I was able to get the values of SigBlk and SigIgn.
Below are the results I have tried.
$ cat /proc/$$/status
Name: bash
State: S (sleeping)
Tgid: 1616
Pid: 1616
PPid: 1615
Uid: 197609 197609 197609 197609
Gid: 197121 197121 197121 197121
VmSize: 6720 kB
VmLck: 0 kB
VmRSS: 10112 kB
VmData: 2880 kB
VmStk: 0 kB
VmExe: 64 kB
VmLib: 4672 kB
SigPnd: 0000000000000000
SigBlk: 0000000000080000
SigIgn: 0000000000320004
$
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Values for SigBlk and SigIgn are zero in /proc/$$/status
2022-03-02 3:47 ` Ken SATO
@ 2022-03-02 9:51 ` Corinna Vinschen
0 siblings, 0 replies; 5+ messages in thread
From: Corinna Vinschen @ 2022-03-02 9:51 UTC (permalink / raw)
To: cygwin
On Mar 2 12:47, Ken SATO wrote:
> Tue, 1 Mar 2022 20:46:54 +0100
> Corinna Vinschen wrote:
>
> > I had a few spare cycles today so I took a stab at it and implemented
> > it. I uploaded new developer snapshots to https://cygwin.com/snapshots/,
> > please give it a try.
>
> Thank you for providing the snapshot.
> I was able to get the values of SigBlk and SigIgn.
>
> Below are the results I have tried.
>
> $ cat /proc/$$/status
> Name: bash
> State: S (sleeping)
> Tgid: 1616
> Pid: 1616
> PPid: 1615
> Uid: 197609 197609 197609 197609
> Gid: 197121 197121 197121 197121
> VmSize: 6720 kB
> VmLck: 0 kB
> VmRSS: 10112 kB
> VmData: 2880 kB
> VmStk: 0 kB
> VmExe: 64 kB
> VmLib: 4672 kB
> SigPnd: 0000000000000000
> SigBlk: 0000000000080000
> SigIgn: 0000000000320004
> $
Great, thanks for testing!
Corinna
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-03-02 9:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-01 5:35 Values for SigBlk and SigIgn are zero in /proc/$$/status Ken SATO
2022-03-01 11:06 ` Corinna Vinschen
2022-03-01 19:46 ` Corinna Vinschen
2022-03-02 3:47 ` Ken SATO
2022-03-02 9:51 ` Corinna Vinschen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).