From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Values for SigBlk and SigIgn are zero in /proc/$$/status
Date: Tue, 1 Mar 2022 12:06:42 +0100 [thread overview]
Message-ID: <Yh3+QvIa1YmnStdG@calimero.vinschen.de> (raw)
In-Reply-To: <TYZPR03MB567866D8526F0F52CE4287BCB5029@TYZPR03MB5678.apcprd03.prod.outlook.com>
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
next prev parent reply other threads:[~2022-03-01 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 5:35 Ken SATO
2022-03-01 11:06 ` Corinna Vinschen [this message]
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=Yh3+QvIa1YmnStdG@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).