Hi! Wolfram Gloger wrote:
>>Besides that, you must never use >>exit() in a forked child that did not exec properly, because it may >>wreak havoc on your stdio/iostream buffers, > > > I think not, if all fd's have been closed, but see above. > > >>signal handlers, allocated >>memory and the like. > > > That would be news to me, but.. You never know who's set an atexit() handler or something like that, in particular when you have a GUI program. I already have seen strange things happening, in particular with threaded programs. >>* r105, finally, contains the compatibility patch for the latest ffmpeg >>trunk (libavformat >= 52.0.0). Sorry, I cancelled the commit because I hadn't updated the Changelog, and then forgot to issue it again. Should be fixed by now. -- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ DVBCUT-user mailing list DVBCUT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-user
