gcc doesn't show up as a defunct process but it won't go away either. I did a ctrl+c on a compile in a terminal and it gave me the "signal caught still cleaning up message" after a minute It was still there. I did ctrl+c a few more times still there. I tried kill -9, logging out and back in... it seems to have a parent of init.
Created attachment 88623 [details] emerge info my emerge info
post the output of `ps aux`
Created attachment 88625 [details] output of ps -aux to save some space on this page and make my life easier i put ps -aux into a file and attached it... I can copy and paste it though if that is preferred.
so you should be able to just `kill -9` it
I SHOULD... but it doesn't kill it.. I've tried kill -9 17811 like 20 times. that's the bug... kill -9 isn't killing it. I suppose it could be a bug with kill (or whatever package kill comes with) but it's not working. If it was I would not have filed a bug. If I can provide anymore info I will...
did you run the kill as root ? if so, it's a bug in the kernel/hardware
ran as sudo aterm... so... yes root. bug in the kernel? nice... should I give anymore info then?
Sorry for the delay here. Couple more questions: *) does this problem still exists or did it vanish with more recent kernels (2.6.21, that is)? *) if it persists, does it occur frequently, if so, how often? *) can we get dmesg after your kill -9? *) /proc/<pidof unkillable gcc here>/status would be useful *) a fresh ps ax would be nice *) take a cookie while we're working on it (aka thanks) :)
I've never seen this before or since. I assume it was a random bug. that is either hard to trigger or has been fixed. I'm going to resolve cantfix on this because I don't have anymore info to give on it, and I consider it extremely intermittent.
