fvwm leaving defunct processes?

["Paul Smith" <pausmith@nortelnetworks.com>]

Has anyone else noticed fvwm leaving defunct processes?  Ever single
application I start from fvwm, either modules or with Exec, is left as
<defunct> after it exits.  It doesn't seem to matter whether I use "Exec
foo" or "Exec exec foo".  The parent of the defunct processes is,
correctly, fvwm itself.

I have been using fvwm for years and years and I haven't changed
anything about my configuration in quite a while; I don't know exactly
how long this has been going on.


I'm using Debian 3.0, with a tiny bit of testing thrown in, and so had
been using fvwm 2.4.8 but I upgraded to unstable fvwm 2.4.10-2 just
recently and restarted, and I still see the same problem...

Is this a libc thing?  Or a fvwm thing (seems like someone else would
have noticed it by now!)?

Ideas on how to fix this?  It's most annoying!

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <pausmith@nortelnetworks.com> HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.