On Thu, Nov 14, 2013 at 7:53 AM, Peter Denison <bug-repo...@marshadder.org>wrote:
> On Thu, 14 Nov 2013, Daniel Kahn Gillmor wrote: > > On 11/13/2013 04:44 PM, Mirco Bauer wrote: >> >>> Please run and paste the output of this command: >>> >>> grep SigBlk /proc/self/status >>> >> >> Who are you asking to run this, Mirco? You had me in the To: field, so >> i'm assuming you're asking me, but i've been unable to replicate the >> issue. fwiw, here's what i get: >> >> 0 dkg@alice:~$ grep SigBlk /proc/self/status >> SigBlk: 0000000000000000 >> 0 dkg@alice:~$ >> >> hth, >> >> --dkg >> > > # grep SigBlk /proc/self/status > SigBlk: b76ef098366ac05c > > This is true both for /proc/self/status and /proc/<pid>/status, where pid > is the stuck gacutil.exe process Ok, this is your problem then, as it is supported to be 0000000000000000. Something has tainted your environment. It is not so easy to find out which parent process did this (the signal block mask is inherited to child processes like environment variables). For some background of this issue can be found in #499569 as I ran into that issue myself some years ago and it took months to figure it out. So this not an issue with Mono runtime but something on your system that affects Mono and also other applications that rely on signals. You basically need to find the process that modifies the signal block mask (non 0s) and it must be one of the parent processes of your terminal or wherever you run the grep command. -- Best regards, Mirco 'meebey' Bauer FOSS Developer mee...@meebey.net https://www.meebey.net/ Debian Developer mee...@debian.org http://www.debian.org/ GNOME Foundation Member mmmba...@gnome.org http://www.gnome.org/ PGP-Key ID 0xEEF946C8 https://meebey.net/pubkey.asc
