From: Ken SATO <ken.294946@outlook.jp>
To: cygwin@cygwin.com
Subject: Values for SigBlk and SigIgn are zero in /proc/$$/status
Date: Tue, 01 Mar 2022 14:35:15 +0900 [thread overview]
Message-ID: <TYZPR03MB567866D8526F0F52CE4287BCB5029@TYZPR03MB5678.apcprd03.prod.outlook.com> (raw)
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
$
next reply other threads:[~2022-03-01 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 5:35 Ken SATO [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TYZPR03MB567866D8526F0F52CE4287BCB5029@TYZPR03MB5678.apcprd03.prod.outlook.com \
--to=ken.294946@outlook.jp \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).