[kde-freebsd] unkillable multithreaded processes stuckin `STOP' state

[Anish Mistry]

On Thursday 21 October 2004 05:54 pm, Marc Ramirez wrote:
> On Thursday 21 October 2004 04:26 pm, Michael Nottebrock wrote:
> > On Thursday, 21. October 2004 21:23, Mikhail Teterin wrote:
> > > Hello!
> > >
> > > This happened twice already -- first with KMail and now with Kontact.
> > > A process crashes as usual (KDE's 3.3.0 release was of unusually low
> > > quality), and seems to go away, except it does not. It stays in the
> > > `STOP' (according to top(1)) or in the `T' (as per ps(1)) state and
> > > can not be killed -- neither with -CONT, nor with -KILL.
> >
> > [...]
> >
> > > This is all, probably, due to something in KDE's attempts to capture
> > > crashes and collect backtraces for better bug reports. But whatever
> > > bugs they may have there, having an unkillable process -- of any kind
> > > -- worries me greatly. Is this a known issue, or is a PR warranted?
> >
> > There have been no similar reports (to my knowledge) and I haven't seen
> > anything similar on either 4.x or 5.x (I don't run 6-CURRENT).
>
> I'm seeing something similar with OpenOffice.  I'm in the process of
> building a kernel with kdb to try to diagnose.
>
Just wanted to add a me too.  I've seen this with KMail a few days ago.

-- 
Anish Mistry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041021/fa0def57/attachment.bin