![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Jun. 1st, 2009
Side effects
Jun. 1st, 2009 02:01 pmНенавиджу коли бібліотеки щось роблять без мого відома...
"run expects to own all the signals in the process. If you set up signal handling, this is not the method for you. (In practice, the only signals that matter are SIGCHLD and SIGPIPE signals)."
"runOnce aborts waiting for a connection request and returns immediately if the process receives a signal. Note that unless you have a handler for that signal, the signal will probably kill the whole process, so set up a signal handler — even one that does nothing — if you want to exploit this."
Стандартно оброблювачі сигналів встановлювались у мене одразу після форка. Тепер їх прийшлось відкласти аж до старту всіх плагінів...
"run expects to own all the signals in the process. If you set up signal handling, this is not the method for you. (In practice, the only signals that matter are SIGCHLD and SIGPIPE signals)."
"runOnce aborts waiting for a connection request and returns immediately if the process receives a signal. Note that unless you have a handler for that signal, the signal will probably kill the whole process, so set up a signal handler — even one that does nothing — if you want to exploit this."
Стандартно оброблювачі сигналів встановлювались у мене одразу після форка. Тепер їх прийшлось відкласти аж до старту всіх плагінів...
Непогана стаття
Jun. 1st, 2009 03:06 pmLinking 101
Recently, I see more and more people having trouble with link-time errors—as if such an error is the worst kind of luck and cannot be fixed by mere mortals. There are many possible reasons, including Java as default language in universities, and alarming spread of header-only-philia, but that's for another post. Here, I want to give a simple diagnostic procedure for link-time errors.
Ніколи до цього не використовував LD_DEBUG. Виявляється, дуже прикольна штука. Ну і --save-temps - іноді цікаво подивитись що ж там препроцесор напрепроцесив. А так, в принципі, все описане я знав.
Recently, I see more and more people having trouble with link-time errors—as if such an error is the worst kind of luck and cannot be fixed by mere mortals. There are many possible reasons, including Java as default language in universities, and alarming spread of header-only-philia, but that's for another post. Here, I want to give a simple diagnostic procedure for link-time errors.
Ніколи до цього не використовував LD_DEBUG. Виявляється, дуже прикольна штука. Ну і --save-temps - іноді цікаво подивитись що ж там препроцесор напрепроцесив. А так, в принципі, все описане я знав.