> You can use wrappers which save the old signal handlers and install new
> ones which clean up after your plugins and return. Doing so, and thereby
> learning the hard way what "clean up after your plugins" entails (unless
> you were very careful designing and writing them in the first place), will
> teach you why nobody tries to automatically handle it for you. (In the
> general case, your plugin has to track *everything* so it can unwind (or
> commit, as appropriate) memory and resource allocations on signal.)
So unless I'm using something like Qt which can catch the signals and
run it's own code to call back to my code and then shut itself down,
I'm pretty much SOL.