[maemo-developers] gtkmozembed: why kill itself in destructor?
From: Eero Tamminen eero.tamminen at nokia.comDate: Wed Jan 14 19:34:50 EET 2009
- Previous message: gtkmozembed: why kill itself in destructor?
- Next message: Qt to be available under the terms of the LGPL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, ext Marius Gedminas wrote: >>> kill (pid, SIGUSR1); >>> kill (pid, SIGKILL); >>> } >>> >>> Why shall we kill pid in the end? Can't the program exit normally? >> AFAIK it can be quite a bit faster. >> >> Normal process exit goes through a lot of destructor code, >> freeing things that are anyway freed by the operating system >> when process terminates. Browser is threaded, so maybe that >> the destructors use locking too... > > That's what the _exit() function from <unistd.h> is for, isn't it? I guess it could be used instead. Maybe somebody wants to file a bug? (I think that unlike SIGKILL, debugger can catch _exit()) - Eero
- Previous message: gtkmozembed: why kill itself in destructor?
- Next message: Qt to be available under the terms of the LGPL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]